alexgso

Hi zappoboy,

You mentioned this happens with new SiteOrigin Editor widgets, but not previously created ones. Does this happen no matter what you add to the widget, or only after adding specific text?

You mentioned you’re using a plugin called Defender. Is this that plugin?
Security plugins often ignore the plugin activation system and instead refer to their own settings whether or not to function. This means that disabling the plugin, won’t prevent it from applying. I recommend disabling the WAF briefly to see if that allows you to perform

Kind regards,
Alex

Hi sladzana,

Thanks for reaching out. The get_header function in WordPress is an important part of themes and is included in all WordPress installs post 1.5.0. That function not being available is a sign of a corrupted WordPress install.

Consider reinstalling WordPress. Before proceeding, do a backup of your website. Then navigate to Dashboard > Updates and click the Reinstall Now button.

Kind regards,
Alex

Hi,

Thanks for reaching out. I’ve run a few tests, and I’m noticing very inconsistent results with justified in the current version and old versions dating back to 2017. I’m going to flag this setting for review. Based on your desired layout, I recommend setting the alignment to Center to see how that looks on your end as that should result in the desired setup.

For more overall options with alignment, I recommend switching to the SiteOrigin Button Grid Widget. This widget can be enabled by navigating to Plugins > SiteOrigin Widgets.

Kind regards,
Alex

Hi Artur,

It’s great to hear you were able to get it working. The change you outlined omits the search query from the translation string which can make translating this text tricker. Did you alter this translation? If so, what did you set it to?

I recommend making your change using a child theme to ensure it’s update safe.

Kind regards,
Alex

Hi Artur,

I’ve investigated this report, and I can’t replicate this issue. I’ve had a look at your site and it appears to be working as expected. Is this issue currently occurring? If so, try reinstalling the theme to see if that helps. This can be done by navigating to Appearance > Themes, and changing to a different theme. Click the SiteOrigin Unwind thumbnail and click delete. Click Add New, and search for SiteOrigin Unwind. Install and active it. Does the error still occur?

Kind regards,
Alex

Hi,

A 404 in an area like the customizer or post editor, is a common sign of the server, or a security plugin, rejecting the request. If Wordfence is active, try temporarily putting it into Firewall Learning Mode.

If you don’t have Wordfence active, please reach out to your hosting provider and ask if mod_security (or an equivalent) is active, and if so, are you getting blocked by it?

Kind regards,
Alex

Hi Pribe,

Thanks for reaching out. You can modify the number of posts per page in Vantage by navigating to Settings > Reading and adjust the Blog Pages Show at Most setting to your desired number of posts per page.

Kind regards,
Alex

Hi King,

Thanks for reaching out. Unfortunately, the issue you’re facing is unrelated to our plugin and is instead related to your theme. It’s not clear who the developer of your theme is based on the theme name, but it’s a theme you purchased from ThemeForest so you should be able to track them down there.

Recovery mode normally allows you to deactivate a theme. Does it fail to deactivate when you attempt to? If so, I recommend reaching out to your hosting proider to ask them to remove the theme. That’ll allow WordPress to leave recovery mode. Best of luck with resolving the issue you’re facing, and I’m sorry it happened.

Kind regards,
Alex

Hi,

Thanks for reaching out. Based on the provided screenshot, it appears as though there’s a series of empty SiteOrigin Editor widgets present on the page you’re working on. It’s not clear how this could happen without input. Page Builder doesn’t directly have anything in place to add Editor widgets to a layout automatically outside of a page conversion – which will can only happen after a manual action in the admin.

Can you please link me to the page you’re working on, and provide me with a copy of the page? This will allow me to inspect your layout and run a few tests. You can export a page by opening the page in the editor and clicking the Layouts button in the Page Builder toolbar. Open the Import/Export tab and click Download Layout. Please upload the file to somewhere like WeTransfer (no email required) and reply with a link.

Kind regards,
Alex

Hi @klenshop,

Thanks for running the test. I’m not familiar with that plugin. A quick look at it however suggests its code should be specific to its custom post type. I recommend checking with the author of that plugin to check if there’s a way to prevent the visual email builder code from loading elsewhere.

Kind regards,
Alex

Hi,

Thanks for reaching out. The provided screenshot is a common sign of a plugin conflict. Would you mind running a quick plugin conflict test?

You can start by disabling all non-SiteOrigin plugins and see if this fixes the issue. You’ll need to clear all your caches after disabling your plugins. So just to confirm, double check if the issue is coming up while all other plugins are disabled.

If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue.Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.

You could also try temporarily switching to a default WordPress theme like Twenty Sixteen. Default WordPress themes are generally very light weight which lowers the chance that they’ll conflict with plugins, so they’re a good way to test if your original theme is the source of the issue.

Kind regards,
Alex

Hi Chris,

It’s great to hear that helped. Please feel free to open a new thread if anything else comes up. Thanks mate.

Kind regards,
Alex

Hi Chris,

I’ve investigated this issue and come up with a fix. You can download a patched version of Page Builder by clicking here.

Before proceeding, do a backup.

Navigate to Plugins > Installed Plugins and deactivate Page Builder by SiteOrigin, and then delete it. Scroll to the top of the page and click Add New, Upload Plugin. Upload siteorigin-panels.2.29.18-beta.zip and when prompted, activate it. The TypeError will no longer occur.

Kind regards,
Alex

Hi itapress,

Thank you for the report. This will be fixed in an upcoming Page Builder update.

Kind regards,
Alex

Hi Everyone,

I can confirm I was able to resolve this issue in Chrome by updating to the latest version. If you’re still facing this issue, I recommend following the steps outlined by Andrew or reaching out to the developers of the browser you’re using for assistance.

Kind regards,
Alex