Home>Support>Images not showing when editing with SiteOrigin Editor

Images not showing when editing with SiteOrigin Editor

Images are not showing when editing with SiteOrigin Editor.

I can see it in the HTML. and it shows on the public site. Just nothing when editing.

WordPress 5.3.2 running Create theme.

https://imagesourceusa.com/wp-content/uploads/2020/03/Screenshot_8.jpg

https://imagesourceusa.com/wp-content/uploads/2020/03/Screenshot_10.jpg

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    Hi Bruce

    Thanks for reaching out.

    The screenshot URL’s don’t appear to be working for us at the moment. Do you have a page we can check where the issue is occurring? If so, please, let us know where on the page to check.

  2. 4 years, 6 months ago Bruce Herwig

    https://imagesourceusa.com/free-mobile-work-force-assessment/

    You can see the image showing as a user.

    You just can’t see them as a an editor in WordPress. the HTML show in text mode. But when you switch to visual, no graphics show.

    PS We block certain countries…so that may be why you can’t access it.

  3. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    Thanks, it sounds like Page Builder is encountering an error. To confirm, please, take a screenshot of the issue in WordPress, upload to imgur.com and send us the link. Thanks.

  4. 4 years, 6 months ago Bruce Herwig

    Here are two screenshots as requested.

    https://imgur.com/Y6vb9Uk

    https://imgur.com/JLWX9Q5

  5. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    Thanks. That I haven’t seen occur before. There a number of ways we can troubleshoot this. If you’d like to click LayoutsImport/ExportDownload Layout, take the JSON file and upload it to wetranfer.com (no email required) and send us the link. We can test to see if the same happens to us locally with the same layout.

  6. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    One step you might first try is to temporarily deactivate Photon. Go to JetpackSettings, I forget what the module is called now, it’ll be under image performance or perhaps if you search Photon, the old module name it’ll appear. Try temporarily deactivating that module and see if the issue persists.

  7. 4 years, 6 months ago Bruce Herwig

    I tried deactivating photo (they now call it the site accelerator) and it stopped showing the featured image at the top of the page. It also didn’t fix the issue, so I turned it back on.

    I believe this the JSON file you are looking for
    https://we.tl/t-0wUbDNkpNm

  8. 4 years, 6 months ago Bruce Herwig

    Same thing, long link
    https://wetransfer.com/downloads/cc500742f9a36581ab3f2a12d71877c820200318190138/8519439bc2b3e14fbdf52ccf595c540f20200318190200/dea13e

  9. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    Thanks, the JSON file doesn’t appear to be properly formatted. You can test it by creating a new page and importing the file via the same process.

    It’s worth running a quick plugin test at this stage. Temporarily deactivate all plugins not authored by SiteOrigin in one go and see if the issue resolves. If you make use of a caching or optimization plugin like Autoptimize, clear it first before deactivation of all non-SiteOrigin plugins.

    It’s also worth creating a new Editor widget on a new page to see if the issue is generally persisting.

  10. 4 years, 6 months ago Bruce Herwig

    I created a new page and the problem persists. So it’s not page specific.

    can you please give me more complete instructions on getting you the JSON?

    Your instructions are clear, but I don’t know where to start?

    Where is the “Layouts” area you mention?

    Is it on the page? or is it in the task bar area?

  11. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    Thanks for trying a new page.

    Please, try a plugin conflict test. Temporarily deactivate all plugins not authored by SiteOrigin in one go and see if the issue resolves. If you make use of a caching or optimization plugin like Autoptimize, clear it first before deactivation of all non-SiteOrigin plugins.

    Layouts is in the Page Builder top bar when editing the page, you’ve most likely exported the layout correctly which is why the above test is a good place to start.

    https://imgur.com/a/OPmniXR

  12. 4 years, 6 months ago Bruce Herwig

    Here is the correctly exported JSON file
    Download link
    https://we.tl/t-03nkLuqc87

    I can’t seem to find the list of plugins authored by SiteOrigin. Do you have a link?

  13. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    When viewing the Plugins list in WordPress there is an author listed for each plugin. Our plugins are Page Builder by SiteOrigin, the SiteOrigin Widgets Bundle and perhaps SiteOrigin CSS.

  14. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    Before running the plugin conflict test. View the page in question in WordPress. Open the browser console and check for errors, here is how https://wordpress.org/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis. Are there errors present? They will be displayed in red.

  15. 4 years, 6 months ago Bruce Herwig

    https://imgur.com/EGnP9lO

    Yes, there are two red errors.

  16. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    404 means not found.

    If you try browsing directly to the image, it isn’t viewable, it should be.

    https://imagesourceusa.com/wp-content/uploads/2020/03/VEIT-1.jpg

    In your Media Library, when you browse to this image and edit it, is the URL provided the same as the URL above?

  17. 4 years, 6 months ago Bruce Herwig

    When I view the page and right mouse click and “”copy image address”” this is what I get

    https://i2.wp.com/imagesourceusa.com/wp-content/uploads/2020/03/VEIT-1.jpg?w=650&ssl=1

    https://i1.wp.com/imagesourceusa.com/wp-content/uploads/2020/03/Visual-Edge-IT-Logo.png?resize=600%2C217&ssl=1

  18. 4 years, 6 months ago Bruce Herwig

    The HTML in the Site Origin Editor is pointing to a different place.

    https://imagesourceusa.com/wp-content/uploads/2020/03/VEIT-1.jpg

    https://imagesourceusa.com/wp-content/uploads/2020/03/Visual-Edge-IT-Logo-400×145.png

  19. 4 years, 6 months ago Bruce Herwig

    When I go into the Media Library and edit the image I get

    https://imagesourceusa.com/wp-content/uploads/2020/03/VEIT-1-1.jpg

    https://imagesourceusa.com/wp-content/uploads/2020/03/Visual-Edge-IT-Logo.png

  20. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    The URLs are formed like that due to Jetpack. The image should still be accessible at its original URL though.

    As an example, I’ve enabled Photon here https://demo.siteorigin.com/corp/. Locate the image next to BUILD STUNNING LAYOUTS
    WITH PAGE BUILDER BY SITEORIGIN. Inspect the page, see the URL is formed with i2.wp.com etc. Then try accessing that same image at it’s original URL https://demo.siteorigin.com/corp/files/2018/04/page-builder-layout.png. The image is accessible.

    Please, let me know:
    In your Media Library, when you browse to this image and edit it, is the URL provided the same as the URL above (https://imagesourceusa.com/wp-content/uploads/2020/03/Screenshot_8.jpg)?

    Next:
    To troubleshoot the issue, temporarily deactivate all plugins not authored by SiteOrigin. Caching plugins should be cleared first. See if you can find a working baseline. If you can’t find a working baseline, if the issue persists with all non-SiteOrigin plugins deactivated, reach out to your hosting company, explain the issue with images and the console log, ask if they can check their logs and see if there is a reason why

  21. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    Super, thanks. So the URL in the Editor is correct. Next, run the conflict test. If no working baseline can be found and the 404 console error persists, please, ask your asks to check ModSecurity logs to see if there are any issues there.

  22. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    The above should have read, “if a working baseline can’t be found”

    Thanks

  23. 4 years, 6 months ago Bruce Herwig

    It took some time but we discovered it was the WebP Express plugin that was causing the issue.

    I’ll reach out to them and let them know there is an issue with view images when editing with SiteOrigin they need to fix.

  24. 4 years, 6 months ago Andrew Misplon
    Hi, I Work Here

    Glad to hear you’re making progress. To confirm the issue, temporarily deactivate all plugins except for WebP Express and Page Builder. That’ll help you confirm that there isn’t a three-way issue happening. Hopefully, the plugin authors can shed some light on what the issue is. If you’d like to help their testing, please, run the plugin conflict confirmation test above, only their plugin and Page Builder. If the issue persists try inserting an Editor widget into a sidebar area at Appearance > Widgets. That’ll narrow down where the issue occurs.

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More