Angela Bowman
Forum Replies Created
-
Thanks, per the email instructions to use CSS to display those hidden fields, I could authenticate manually.
To be clear, YOUR server returns a 403 from Cloudflare after going to Stripe.
This has nothing to do with the website server, but perhaps different website servers may respond differently to this failure on your end.
You simply need to adjust how Cloudflare responds to and/or use a subdomain for these requests. The way RCP’s CF is responding is the source of the issue and shouldn’t take many months to fix.
To be clear:
Stripe Connect fails because your Cloudflare is blocking credential retrieval.@markussss – Agree. I did use #wpadminbar and that worked for me recently.
Hi Abhay,
We see this issue as well on the Uncanny Groups Management page and any pages that also use DataTables. Wallet is outputting its DataTables unconditionally on all frontend pages, even where the Wallet plugin is not being used.
I am de-enqueuing the Wallet DataTables script on specific pages, but it would be best for performance to not have this being applied to all frontend pages.
Thanks,
Angela
Thanks so much! I was just confused about the plan since it didn’t come out in 3.1.1. Appreciate the quick response.
Forum: Plugins
In reply to: [Breadcrumb NavXT] Breadcrumbs desappeared after updatingMy comment was removed. I do not need support, dear moderator. I am concurring with the OP that this update causes breadcrumbs to disappear from sites. People should be allowed to comment on forum posts to participate in the discussion. I indicated that I wanted to follow this thread. No need to remove my comment. I am here to follow.
Forum: Plugins
In reply to: [The Events Calendar] Site down after last updating 6.5.1.5@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.
- Toggling that off does not effect fatal error. I always have that toggled off.
- 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.
- 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.