alexgso
Forum Replies Created
-
Forum: Plugins
In reply to: [Page Builder by SiteOrigin] Update 2.29.12 Fatale errorHi Ralf,
Yes, that’s the correct contact form. That’s okay. ??Kind regards,
AlexForum: Plugins
In reply to: [Page Builder by SiteOrigin] Update 2.29.12 Fatale errorHi Ralf,
I’m investigating this issue and I’m having trouble replicating it. Would it be possible for you to reach out to us via our contact form on our website?
Kind regards,
AlexForum: Plugins
In reply to: [Page Builder by SiteOrigin] Fatal error on premium builderHi mo123z,
Thanks for reaching out. I’m very sorry to see you’re experiencing an error. I’ve investigated this issue, and come up with a fix. Please email [email protected] with a copy of your license key, and I’ll provide you with a patched version before the next update.
Kind regards,
AlexForum: Plugins
In reply to: [Page Builder by SiteOrigin] Attempt Block Recovery – SiteOrigin Layout BlockHi,
It’s great to hear that helped. This change will be included in an upcoming Page Builder update. Please feel free to post a new thread if anything else comes up.
Kind regards,
AlexForum: Plugins
In reply to: [Page Builder by SiteOrigin] Attempt Block Recovery – SiteOrigin Layout BlockHi,
Thanks for reaching out. I’m working on an update that should prevent this from happening, and I’ve prepared a patched version for you to try.
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.12-beta.zip, and when prompted, activate the plugin.
Kind regards,
AlexForum: Plugins
In reply to: [Page Builder by SiteOrigin] Shortcode issue since 2.29.6Hi Grupa,
We’ve identified a fix for this issue, and I’ve prepared a beta build for you to try. You can download it by clicking here.
Once downloaded, do a backup.
Navigate to Plugins > Installed Plugins and deactivate Page Builder, by SiteOrigin. Delete Page Builder and then scroll to the top of the page. Click Add New, Upload Plugin and upload siteorigin-panels.2.29.9-beta.zip.
Kind regards,
AlexHi virtualgeo,
I’ve devised a potential fix for this and prepared a build for you. You can download it by clicking here.
Before proceeding, do a backup.
Navigate to Plugins > Installed Plugins, and deactivate the SiteOrigin Widgets Bundle, and then delete it. Scroll to the top of the page and click Add New, Upload Plugin. How does that look?
Kind regards,
AlexHi,
With the modified shortcode, I’m having trouble replicating the described issue while using the Block Editor (or Classic Editor). Can you please try the provided snippet to see if that works for you?
If it doesn’t, can you please provide me with an export of the layout you’re working on? This will allow me to run some tests directly against that page. Please upload the export to Pastebin.
My problem seems to be solved by commenting out line 125 ( // $GLOBALS[ ‘SITEORIGIN_PANELS_POST_CONTENT_RENDER’ ] = true; ).
This line was intentionally added to help with rendering things more consistently overall with the Classic Editor. In other words, it brings it in line with how we typically render pages.
Kind regards,
AlexHi virtualgeo,
Thank you for a copy of your shortcode. I’ve run a few tests using it, and I can’t seem to get it to work in any context. Looking over the code, it’s not set to output the content of the shortcode and instead only set to output an element. I’ve made some code changes to output the content, and the widget content is now working as expected for me. You can find the altered code here.
I suspect we’ve resolved a bug that was allowing this shortcode to function as it was. I recommend giving it a try and seeing how it looks on your end. I also recommend giving the escaping data for output a read in the developer handbook.
Kind regards,
AlexForum: Plugins
In reply to: [SiteOrigin Widgets Bundle] Button Onclick returns empty after v1.58.3Hi Shane,
The provided build is a patched version of 1.58.6 so it is not affected by that issue.
Will this fix be rolled out in the next version?
The provided changes will be included in an upcoming release. I’m unable to provide you with an ETA on when that release will be.Is it possible to maintain the OnClick whitelist ourselves or disable it?
It’s not directly possible to modify the allow list at this time, but it is possible to disable it using a filter. This is however not recommended as it poses a security concern. That security concern was why this change was made.
You can disable the disallow list, which will prevent any unintended restricted JavaScript code from being present, using the following PHP:
add_filter( 'siteorigin_widgets_onclick_disallowlist', '__return_false' );
You can disable the allowlist, which is used to restrict the “top level” functions, using the following PHP:
add_filter( 'siteorigin_widgets_onclick_allowlist', '__return_false' );
If you need a method of adding the above code, you can use a plugin like Code Snippets. For your specific onclick usage, both checks will fail. The provided build will allow for both of them to succeed safely.
Kind regards,
AlexForum: Plugins
In reply to: [SiteOrigin Widgets Bundle] Button Onclick returns empty after v1.58.3Hi Shane.
I’ve added Calendly to the whitelist, and created a build for you to use that includes this change. You can download that build by clicking here.
Before proceeding, do a backup.
Navigate to Plugins > Installed Plugins and deactivate SiteOrigin Widgets Bundle and then delete it. Scroll to the top of the page and click Add New, Upload Plugin. Upload so-widgets-bundle.1.49.1-beta.zip and when prompted, activate it.
Kind regards,
Alex- This reply was modified 9 months, 1 week ago by alexgso. Reason: Updated Link
Forum: Plugins
In reply to: [SiteOrigin Widgets Bundle] Fatal Error 1.58.4 for NOT logged in usersHi,
I’ve figured out a way to replicate this issue, and I’ve come up with a fix that resolves this issue for me. This issue is quite inconsistent so we would appreciate it if someone who can replicate this issue could try the fix that would be much appreciated. You can download the patched version by clicking here.
Before proceeding, do a backup.
Navigate to Plugins > Installed Plugins, and deactivate SiteOrigin Widgets Bundle, and then delete it. Scroll to the top of the page and click Add New, Upload Plugin. Upload so-widgets-bundle.1.58.6-beta-2.zip and when prompted activate it.
Kind regards,
AlexForum: Plugins
In reply to: [SiteOrigin Widgets Bundle] Fatal Error 1.58.4 for NOT logged in usersHi,
I’ve come up with a potential fix for this issue. I’ve been unable to replicate this issue after the fix in 1.58.5 so if someone who is affected by this issue could try the fix that would be much appreciated. You can download the patched version by clicking here.
Before proceeding, do a backup.
Navigate to Plugins > Installed Plugins, and deactivate SiteOrigin Widgets Bundle, and then delete it. Scroll to the top of the page and click Add New, Upload Plugin. Upload so-widgets-bundle.1.58.6-beta.zip and when prompted activate it.
Kind regards,
AlexForum: Plugins
In reply to: [SiteOrigin Widgets Bundle] Fatal Error 1.58.4 for NOT logged in usersHi Hunter,
Thanks. The provided layout is working without issue for me. Does this issue occur if you disable all plugins except for SiteOrigin Widgets Bundle, and Elementor?
Kind regards,
AlexForum: Plugins
In reply to: [SiteOrigin Widgets Bundle] Fatal Error 1.58.4 for NOT logged in usersHi Hunter,
Thanks. That appears to be the View Source of the page on the front end rather than the markup in the Block Editor. You can access that by opening that page in the editor. Click the 3 vertical dots at the top right of the screen. Select Code Editor and you’ll see the markup for the current page. Copy the markup and paste it on this page. Please reply with a link to the Pastebin.
SiteOrigin Widget Bundle widgets can be added using Elementor. It should, in theory, work without issue. I’ll need to run some tests using the layout to work out what’s going on.
Kind regards,
Alex