doffine
Forum Replies Created
-
Forum: Plugins
In reply to: [Contact Form 7] Just one autoresponder mail per mail addressHi @takayukister,
thank you very much for coming back to us. We do use spam protection modules for at least to block standard spam bots. This works quite well. But as you say this only mitigates the risk. There might be a more sophisticated spam bot or even a real human that manages to abuse the form.
So wouldn’t it be an idea for a new CF7 feature to add a check box “Send this responder only once in 24h to an individual email address”? Or do you even know CF7 addons already doing something like this?
Thanks again for your time and great work. We rely on CF7 with over 250 installations for years now. Thank you!
Greetings,
-doffine
Hello @jeroenrotty,
now I found some time to try your above solution. I performed all of your steps. But I have to say it didn’t work. Even the reset with the Yoast test helper plugin didn’t remove the notification with the new taxonomy permanently.
It is always enough just to go on the Appearance > Themes page and the notification is instantly back.
We as an agency see this in different Yoast installations on completely different websites and different servers. WordPress versions are most current and PHP is 8.1. What can we do next? This somehow looks like a Yoast bug or perhaps -incompatibility.
Greetings and thank you for your help,
-doffine
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] 404 error in backend console – file missingwe cannot update to version 2.0.0, because version 2.0.0 has some bugs that make it unusable for us as you can see in other entries here in the forum.
Again: The problem is that the installation searches for the file https://[DOMAIN.TLD]/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-compat/assets/js/gzd-compat.js?ver=1.9.5 that causes a 404, because the file is in another location in the package.
Greetings,
-doffineForum: Plugins
In reply to: [WooCommerce PayPal Payments] 404 error in backend console – file missingHello @joostvandevijve,
the 404 shown in the console doesn’t come from âwp-content/plugins/woocommerce-paypal-payments/modules/ppcp-compat/resources/jsâ
It is “GET https://[DOMAIN.TLD]/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-compat/assets/js/gzd-compat.js?ver=1.9.5
[HTTP/2 404 Not Found 917ms]” – and in this location the file is missing in the package.So you write “resources”, but the file obviously is searched in “assets”?
Greetings,
-doffineForum: Plugins
In reply to: [Code Snippets] error The plugin does not have a valid headWe have the same problem. Our agency uses about 250 installations of “Code Snippets” in very heterogenous WordPress installations – installed over the last years on different servers and we didn’t see this problem anywhere so far.
As all of you described before this problem only occurs directly after a new installation of this plugin when we try to activate it right after/from the installation dialog. It doesn’t occur if we activate the plugin from the plugins page.
It happens with PHP 7.4 and PHP 8.1, too. We guess it should be the last update of this plugin that introduced this bug.
We would be happy to read something from the plugin author in this 11 days old thread.
@bungeshea if you wish to reproduce this problem easily just get you a fresh WP installation at wpsandbox.net and only install (and directly activate) your plugin. That’s enough.
Greetings,
-doffineHey @karzin,
we just tried it and yeah, your new version fixes the incompatibility!
You just got your well deserved 5 stars review :).
Greetings and have a nice weekend,
-doffineHey @karzin,
we tried your solution in the Avada Performance Settings and that fixed the problem here, too.
We then noticed that this setting “Load jQuery In Footer” is not the standard setting in a fresh Avada installation and Avada themselves say that one can try to use this setting for performance reasons as long as no plugins conflict with it.
Perhaps for you it might be worth a thought if you could easily change something in your jQuery code to make it compatible to this Avada setting as most other plugins are. For now, we just disabled this setting and for us all is good now. So I’ll mark this here as resolved.
Thanks a lot for your prompt and perfect support,
-doffineHi @karzin,
thanks for coming back so quickly. That’s really cool. Because we don’t use any caching/optimization plugins we only changed the theme to Storefront – and the error was gone.
So your plugin seems to have an incompatibility with the theme Avada that we use.
Is it an incompatibility that you simply can fix on your side? That would be best we guess.
Perhaps it might be possible to make some settings changes in Avada, but we wouldn’t know which ones. Beside this, changing settings in the standard Avada setup just to make it work together with your plugin in the cart would look a bit like the tail wagging the dog (no offense ð ). We think it must be in your own interest that your plugin works with a theme like Avada without any errors straight out of the box.
Since Avada is one of the most widespread themes out there what would you suggest?
Greetings,
-doffineThank you very much. It would be very nice if you think about adding the HTML option to this in future releases.
Marking this as resolved now.
-doffine
Forum: Plugins
In reply to: [Photo Gallery by 10Web - Mobile-Friendly Image Gallery] Source Map ErrorAfter STRG+F5 reloading multiple pages the source map error suddenly is gone. I guess it was a caching problem. I’ll mark this as resolved now. Sorry for this.
-doffine
Forum: Plugins
In reply to: [Contact Form 7] Validation of forms via wp-cli possible?We have the same problem. It is frustrating to re-do validation in several hundrets of installations. It is not the first time we have to do this. Costs much time.
When it really must be that upon new validation rules a re-validation must be done – why can’t this be done automatically by the plugin and the admin is only notified with red badges in case this validation fails?
It is not the most pleasant work, to log into several hundrets of installations just to click some buttons.
Greetings and thanks for the work on this great plugin,
-doffineHello alexgso,
ah, there is a misunderstanding. The shortcode isn’t put in the footer area.
The Woody shortcode is put into a normal page using the SiteOrigin page builder. The shortcode is put in a normal page builder line using a “SiteOrigin Editor” widget there.
The Woody shortcode executes a very simple PHP script that gets POST variables and INSERTs something into the database. This happens twice as long as the shortcode is executed in the SiteOrigin Editor widget.
WordPress is 5.9.3, PHP is 7.4, theme is Virtue Premium.
Greetings,
-doffineI’m sorry we cannot perform this test, because the solution with another widget (Individual HTML) for the shortcode is already in live mode since we found that as a solution yesterday evening. We simply wanted to let you know about this problem although we have found a workaround for us by using another widget. We use your “Page Builder by SiteOrigin” and we have no extra classic editor plugin installed in the WP.
Perhaps the following can also be of interest for you:
– If we put an exit(); at the end of our PHP script, it only gets executed once – but the website’s footer is missing of course.
– If we don’t put the exit(); at the end, it gets executed twice, but the output it echoes is only shown once in the website. It is the second execution that shows it’s output in the website, not the first round.Greetings,
-doffineHey,
I understand and think you will be right. I’ll mark this as resolved here and post in the SiteOrigin support forum.
Thanks for your reply,
-doffineForum: Plugins
In reply to: [Photo Gallery by 10Web - Mobile-Friendly Image Gallery] jQuery Console Errorthanks a lot. I mark this here as resolved now.
Thank you for your work and have a nice day, too,
-doffine