Angela Bowman

@studiolonga – Are you by chance any sort of TEC events widgets/elements in any of your templates? Avada comes with this: https://avada.com/documentation/events-element/

In Elementor, the Legacy Events widget (from TEC) is causing fatal 500 server error due to out of memory issue when used on the Single Post template assigned to events. I removed it, and it solved the issue.

This possibly is not a plugin or theme conflict per se, but a bug within an existing TEC widget/element you may be using. So check all events-related widgets in your Avada page builder and whatever widgets/elements are being used to create the events page. If you use the Events Element on any template pages, you might reach out to Avada and let them know there could be a problem with 6.5.

I have not. I have tried to get traction on it for a couple years now. I might have to have another developer fork this and put in a fix. It’s starting to hamper what we can do.

Thanks, Gustav. I did have screenshot of Console tab and should have shared that, but I had issue with obfuscating the client site details. I am out of the office for post op and dashed this ticket off from recovery bed for a client, so I was doing what I could with my mental capacity being pretty whacked and was in the process of trying to get more details from their IT department who set this all up. I came back to this ticket to add the details they sent to me, but you had already fixed it. Thanks again for the rapid fix.

We have tested, and it all appears to be using correct path now. Thanks for quick response!

Thanks! As for “whoever made this fix actually created a problem instead of fixing a problem” I meant that it caused the problem it was trying to fix, but I understand it fixed the problem for some other use cases. No worries. This happens all the time. Development is like a bag of sand. You fix one thing and break another. Just wanted it to be clear that this “fix” for some broke things for others.

I did share details about the URLs breaking: all TEC CSS and JS files. Since this caused 404 for every TEC CSS and JS file, I didn’t think a screenshot would be of further help.

These URL included the system path, e.g. https://mywebsite.com/directory/directory/wp-content/ instead of https://mywebsite.com/wp-content/

We will test! Thanks for the quick response.

Also, we are willing to contribute and pay to have this fixed.

This does work:

Please go to?NextGEN Gallery > Other options > Image options > Show related images on Posts >?Select?“NO”

However, the Watermark settings are set to use an image by default possibly and if there is no URL for that image, it will not save settings. So set Watermark to text and NO, and then you can save the settings and this will stop the Related Images from showing on every page.

Since NextGEN Gallery/Imagely was sold, it seems the support is not what it used to be.

1. Toggling that off does not effect fatal error. I always have that toggled off.
2. Thanks for dev doc. Setting that filter hook does stop the 500 errors. Note: these errors occurred due to this Yoast cron: wp-cron.php?hooks=wpseo_indexable_index_batch So setting the filter hook in code stops that cron.
3. However, Yoast continues to add SEO Outgoing Links column to the Formidable Forms Views interface regardless of the indexing status being set off in both settings and with filter hook. See screenshot. Why would Yoast insist on adding this column to a post type that it has been set to no index? Again, now with the PHP filter hook, this post type isn’t even visible in Yoast Settings, yet Yoast keeps adding this column here. Why?

Thanks! I wrote here in case anyone else had noticed this issue. I imagine only folks who pay attention to access logs will have been aware of this years’ long issue.

As to the credits issue: Shortpixel right now is “noticing” ALL images uploaded across all forms not just the ones uploaded to the folder in the Custom Media Folders interface. So we are being docked for image optimization for all the images across all the forms currently when I do a scan. So it does optimize FF images when a manual scan is done, but it does it across all form folders as well as throws 404s for the non existent folder. It’s all a bit of a mess.

I’ll comment here when the support team fixes, so that others will know when it is fixed.

This is a bug introduced in WordPress 6.4.3 in which Mac OS zip archives won’t work with WordPress. So all theme and plugin developers are scrambling to re-zip their files and re-upload. So re-downloading the pro plugin will allow you to upload if they fixed it.

This is a bug introduced in WordPress 6.4.3 in which Mac OS zip archives won’t work with WordPress. So all theme and plugin developers are scrambling to re-zip their files and re-upload. So re-downloading the pro plugin will allow you to upload.

I updated Site Kit to latest version, and the issue is resolved. Thanks for the prompt response, Adam.

Thanks for that additional input! Yes, and the simpler workaround I realize is this:

BEFORE editing the page with Elementor, REMOVE the Classic Editor block on that page, so the WordPress edit page is BLANK. Then update the page.

THEN you can edit with Elementor just fine and manually insert the shortcode using Elementor’s shortcode widget.

So no need to create a whole new page. That just circumvented the issue you described with rendering that shortcode when it tried to automatically bring it in from the WordPress page content.

I should add that when I originally encountered the issue, I didn’t have the Javascript issue and things appeared to be fine, but it was only upon saving the Elementor page that I encountered the PHP error, and even if I removed the auto generated block that came over, it still threw the PHP error.

Now it is limited to a Javascript error, and deleting the content that Elementor brings over from the page fixes it as well. Not sure what shifted, but all is well with the workaround.

• This reply was modified 9 months, 3 weeks ago by Angela Bowman.

This is not an edge case issue. I did some more testing and found this is a PHP 8 issue. Is GiveWP not supporting PHP 8 yet?

I can reliable reproduce on any site running PHP 8.x and only GiveWP plugin. It works fine with PHP 7.4.

Here is a Loom: https://www.loom.com/share/ffb4696f9ea7449295396b3369897de7?sid=8698bed8-f6d8-4c45-9da4-6b71c499baa4

I would not put this off as an edge case. Bulk editing posts and pages is a normal WordPress activity and Give should not be throwing PHP errors when that is done.

Clarification on steps to reproduce:

1. Latest version of WordPress, GiveWP, and Elementor Free version.
2. NEW INSTALL of GiveWP (fresh fresh fresh) in which you go through the GiveWP onboarding, and GiveWP automatically installs all of the pages needed for GiveWP.
3. Edit the Donation Confirmation page in Elementor (aka the Success page). On one site, I got a Fatal Error as indicated above when saving the Elementor layout. On another site, the page never loads properly. And there is a Javascript error, so I never got to save the page (see error below).
4. To workaround this issue: Create a NEW WordPress page for the Donation confirmation and change the GiveWP Settings for the Success page to use this new page, then you can edit fine in Elementor.

So the issue appears to only be a problem, strangely, with the Donation Confirmation page that GiveWP auto generates. Here is a Loom video demonstrating this:

https://www.loom.com/share/60d1926d8e124481831eb48946ae13c1?sid=d4641fb5-5755-496d-941d-0a73ddfaff16

The Javascript error when the Elementor edit page interface is open on the Donation Confirmation page that Give creates. I should add I’ve tested in Elementor 3.18.3, 3.19, 3.19.1, and 3.19.2.

TypeError: e.O is not a function
    at https://askwpgirldemo.sitedistrict.com/wp-content/plugins/elementor/assets/js/frontend.min.js:2:40210
    at webpackJsonpCallback (https://askwpgirldemo.sitedistrict.com/wp-content/plugins/elementor/assets/js/styleguide-app-initiator.min.js:3:12265)
    at webpackJsonpCallback (https://askwpgirldemo.sitedistrict.com/wp-content/plugins/elementor/assets/js/webpack.runtime.min.js:2:4680)
    at https://askwpgirldemo.sitedistrict.com/wp-content/plugins/elementor/assets/js/frontend.min.js:2:74

There is also a PHP warning happening on the site but perhaps unrelated:

PHP Warning:  Cannot assign an empty string to a string offset in /www/wp-content/plugins/give/includes/misc-functions.php on line 2304

• This reply was modified 9 months, 3 weeks ago by Angela Bowman.
• This reply was modified 9 months, 3 weeks ago by Angela Bowman.
• This reply was modified 9 months, 3 weeks ago by Angela Bowman.