Niels Pilon
Forum Replies Created
-
Hi, thanks for the reply. The support feature in the plugin starts an AI-chat which suggest me to use the contact form at https://backwpup.com/support but that page returns a 404. And the same AI-chat on that page also suggests me to go to https://backwpup.com/support So that creates an infinite loop….
Already tried it with a different plugin, WPUpdraft, and these scheduled updates are working just fine.
Thanks for the snippet but unfortunately it doesn’t remove the widget.
Regards, Niels
Hi @kushnamdev
Sure, see the following link with had a screenshot https://www.dropbox.com/s/w9rz351hr9ewf1o/Schermafbeelding%202023-01-06%20om%2009.06.45.png?dl=0
Regards,
Niels
Sorry for the duplicate topic. Thought that the other topic (https://ww.wp.xz.cn/support/?post_type=topic&p=16344406) wasn’t created but it’s also flagged for moderation.
Forum: Plugins
In reply to: [WP Store Locator] Show opening hours at info windowAh, thanks again @farroyob Customising it with CSS shouldn’t be a problem at all.
Forum: Plugins
In reply to: [WP Store Locator] Show opening hours at info windowThanks for your reply @farroyob. I’ve added the openings hours with that snippet.
One more question though, is it true that you can’t change the max-height of the info window? According to https://wpstorelocator.co/document/wpsl_infobox_settings/ there’s no parameter for that setting…?
Hi @belimperial
Thanks for your reply and the posted solution which solved the issue 🙂
Kind regards,
Niels@pamamo Yes I did and it wasn’t anything plugin related.
What happened is that we have security headers enabled. One of these setting was X-Frame-Options set to DENY. After changing it to SAMEORIGIN the errors are all gone.
Hi Mark,
Contacted Gravity Forms and did some further debugging. It seems like it has something to do with ACF and not Gravity Forms or your plugin.
This issue only happens when I’m using a custom Gutenberg block made with ACF which uses the gravity_forms function to render a form.
It happens in a clean WP install too with the default theme and GF and ACF as only installed plugins.
I will contact ACF support to see if they know about this issue.
Kind regards,
NielsHi Mark,
Thanks for your swift reply. I thought so too but just asked the question here to be sure.
I did check similar code on another site when using the ralationship field and above the gform_wrapper an empty line of Javascript like
<script type="text/javascript"></script>was added as well for some reason.I will update this ticked once I’ve got a reply from Gravity Forms 🙂
Hi,
Thanks for the swift reply. I just checked the console and found out the uBlock was interfering and blocking one file… Was not expecting that at all but after disabling uBlock all setup fields are visible.
Thanks!
Niels- This reply was modified 5 years, 2 months ago by Niels Pilon.
Thanks for your rely. I followed the steps and after resetting the indexable tables the issue is resolved 🙂
Hi @pcosta88
Thanks for your reply. To answer all your questions:
- Yes, all plugins are updated except WordPress which is 5.6.2. The theme is a custom one
- We’re using MultilingualPress for translating the content
- Yes, see https://imgur.com/a/pUNlEIf
- Breadcrumbs pathway should be: Home, CPT archive, taxonomy, CPT title. In this case the full breadcrumb path should be: Home -> Gewassen – > Groenten -> Kasgroenten. See also the screenshot with a breadcrumb of the taxonomy page and the single CPT page
Updated: also tesed with WP 5.7 but the issue is still there. However on the dev site which uses the same settings, the issue isn’t there and it shows the correct term title and I can also save the breadcrumb settings so I can override the breadcrumb title if needed. This is odd.
- This reply was modified 5 years, 2 months ago by Niels Pilon.
Hi Thomas,
FYI: I updated WPML to the latest version a couple days ago and the Matomo tag-manager and admin pages are all fine now.
Kind regards,
NielsHi Thomas,
Thanks for your reminder and sorry for not getting back to you sooner. Completely forgot the issue…
I just tried to send a system report and it generated a fatal error as well. However this time I got the notification with debugging info and it mentioned an issue with the WPML plugin:
Een fout van het type E_COMPILE_ERROR werd veroorzaakt op regelnummer 331 van het bestand /home/locatus/public_html/wp-content/plugins/matomo/app/vendor/twig/twig/src/Extension/CoreExtension.php. Foutmelding: Cannot redeclare twig_cycle() (previously declared in /home/locatus/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/twig/twig/lib/Twig/Extension/Core.php:288WPML has an update available so I will update WPML first to see it that solves the 500 errors when accessing Matomo reports.
