Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • @vs_naho Thank you for solving the issue with depicter. Finally got back on the project and was able to implement your solution today. Would be good if the devs provided an area in the plugin settings to add that code and keep it there regardless of updates. Thanks so much again. I could not reply to my own thread.

    Thread Starter ncomp2000

    (@ncomp2000)

    The connect-src blob in the source location (depicter editor) does not show up as a directive in version 1.5.5 which is the reason it worked normally. Now in the latest versions, it does. Not saying that is a bad thing I am just trying to understand why this error is being thrown from that particular line in the screenshot.

    Thread Starter ncomp2000

    (@ncomp2000)

    It’s not crashing and enabling debugging does not help as the only 2 things I see are related to memory but I can confirm that the appropriate amount is being allocated to my WordPress instance. The problem seems to be that blob: is being blocked in the content security policy. I’ve not set anything that would do this.

    Seems like this particular line is being blocked for whatever reason.
    https://pasteboard.co/ncV2fn4Vq6UD.png

    • This reply was modified 3 years, 2 months ago by ncomp2000.
    Thread Starter ncomp2000

    (@ncomp2000)

    Hi can I get a response on this? I believe that the issue is with content security because there is a difference in how the console displays information from the 1.5.5 version to the current version. I have not changed nor do I know what i would need to update with regards to the content security.

    Thread Starter ncomp2000

    (@ncomp2000)

    Forgot to add console information to the last update. This is probably the issue, but I am unsure what changed that it throws this error.
    https://pasteboard.co/BP9TEfJRxP2P.png

    Thread Starter ncomp2000

    (@ncomp2000)

    Update: I just deleted the 2 depicter tables from the database after deleting the plugin itself. I re-installed the newest version of the plugin, and re-imported my saved slider. I was only able to publish it once. After that I still get “Unable to save” for some reason. This also occurs still when importing a template. Will have to revert while another solution is found. I do think this is a good plugin, just not sure why it is not working for me. This is what the plugin looks like when I initially go in. It says unpublished but when it is published, it will not save when editing.
    https://pasteboard.co/yc6gy272EyI4.png

    Thread Starter ncomp2000

    (@ncomp2000)

    Hello, thank you for your response and sorry for the delay. I could not find any posts about this issue either which was strange.

    When I installed Depicter, it was at version 1.5.5. Everything worked as it normally did. I created a slider from scratch, and as I made changes to the elements, they were saved normally after each one like this:
    https://pasteboard.co/BO3Y3j5rlZGt.png

    When I when I performed the plugin update to 1.6.2, I go to the depicter section like normal, and I see the slide that I created with the previous version. Interestingly, it said unpublished so I published it and surprisingly that went through like this:
    https://pasteboard.co/kIM8LbngSjvc.png

    However, when I access my slider to edit it, it has the message “unable to save” by the slider name and the publish changes button is greyed out like so:
    https://pasteboard.co/7y6mVj4tI0OW.png

    I did try setting up a new from scratch slider and a slider from the templates offered however I run into the same issue with those. Its truly strange because version 1.5.5 works fine and with the plugins I have so I don’t think the other plugins are an issue.

    The next thing for me to try is to export the slider and delete everything relating to depicter in the database, deleting the plugin and starting over clean. There wasn’t anything drastic done in my setup between these versions so i’m a bit stumped.

    Thank you for your time in reviewing this.

Viewing 7 replies - 1 through 7 (of 7 total)