sergeyf1
Forum Replies Created
-
Hello,
I really hope you can reply to yesterday’s post, as the problem persists. And even more so, now the Happy Addons templates and blocks are not displayed at all. This is happening in my different clients on different system configurations and versions of Elementor and WordPress. I have tested on a “clean” WordPress installation (Elementor+HappyAddons only) and can confirm the issues. I would appreciate your response and help. Thank you!– Screenshot 1 (Error) – from 11.03.2024
– Screenshot 2 (blank screen instead of Happy Addons templates) – from 12.03.2024Hi @kmacharia,
Thank you for your response. I just created a thread in the WP Hide & Security Enhancer support forum as you requested.
In addition to my previous post, a new screenshot with an explanation
Hi @rsouzaam,
Thank you for your reply, but it is unfortunately incorrect. I wrote in my first post that the problem occurs only when the admin panel has a custom address. That is, it does not have a standard address [/wp-admin/], but a custom address, such as [/wp-manage/]. When a custom address is used for the admin panel, WPForms 1.8.7.2 cannot save the form either when creating or editing it.
I use the [WP Hide & Security Enhancer 2.3.1] plugin on dozens of client sites to create a custom address. And WP Hide & Security + WPForms worked fine until WPForms 1.8.7.x update.
I hope I was able to convey my thoughts correctly and clearly now.
Forum: Plugins
In reply to: [Advanced Custom Fields (ACF®)] Frontend Display and MetaboxYou do bring up an important point and this post seems very timely to me. I partially agree with your arguments that the authors of ACF plugin could probably make the ability to show ACF fields on the front-end more simple and convenient for the vast majority of ACF plugin users. For example, such features could be introduced in the paid version of the ACF Pro plugin.
Most likely you are right when you say that ACF plugin is used most often not by developers, but by “ordinary” users and site authors. They are the ones who make the audience of the ACF plugin so large. But I think that the authors of the ACF plugin may not want to overload the plugin with functionality not directly related to its direct work. Maybe ACF authors want to focus on ACF fields and Admin UI features, and leave the rest of the work (displaying ACF fields data on front-end) to third-party plugins and site authors themselves. This approach has a right to life, but perhaps it should be reconsidered.
Now even the strategy of WordPress itself, with its new block editor and new FSE approach, explicitly says that times have changed, the “average” WordPress user wants more features for less effort. What used to be a way to say “we’re developer-centric or our audience is developers” may be a losing strategy now. Now sites have become more complex, technologies are changing very quickly and sometimes the site author simply may not have the ability to delve deep into the technical documentation of a plugin to use some of its features. This work may be more correct in the new realities to automate and offer it to the end user in a convenient format.
The request for a more convenient and easy display of ACF field data is now high and meets the needs of the plugin audience more than before. I use different solutions for displaying ACF fields in my work, including ACF Views plugin and Elementor Pro. It’s more convenient and easier, but it doesn’t always work as it should, so I have to look for other options, including custom code.
I, like you, wish that ACF plugin authors could implement built-in functions for displaying ACF fields on the front-end, but I think that the problem lies in the reluctance to overload the plugin with additional functions not directly related to the plugin and Admin UI.
Although maybe the authors of ACF plugin should still do it and implement such features, because most of the plugin audience would definitely like it.
I also think it would be better to write your message in the official support channel of the ACF plugin at the following link. It will be more effective in getting your thoughts and request to the authors of the plugin.
Hi Dinesh,
Thank you so much for this notification and for your hard work. I hope you can find a solution that will allow the WP Armour plugin to reliably protect sites from spam again.
I created this thread on November 28th on the forum just to work with you to figure out what the cause of the unexpectedly increased spam flow is. And again I’ll note – just until recently (until November 28th) your plugin demonstrated amazing results in spam protection. The plugin works on 12 client sites. Now WP Armour is still active everywhere.
Very much looking forward to your further updates.
Thanks!Hi Dinesh,
Thank you for being able to take the time to reply to my message. It’s a pity that this forum thread is used by other users off-topic)). After all, I reported problems only with WPForms, and it is not right to write about other plugins here)))).
I apologize for not responding to your message right away. I needed more time to look into it and try to get a deeper understanding of what the problem might be.
I analyzed several client sites (everywhere WPForms + WP Armour with different versions). The spam flow increased dramatically 2 days ago, this also coincided with the latest WPForms update, but apparently the problem is deeper than that.
The only way to stop the flow of spam on the investigated sites was to enable Cloudflare Turnstile. Without that, the spam continues to flow. I don’t know why this happens, perhaps the WPArmour protection has been somehow bypassed by spammers.
On the client sites I left the WPArmour plugin enabled + added additional protection to the forms in WPForms with Cloudflare Turnstile. This solution has been able to stop spammers so far.
If you still need it, I can email you the credentials (login+password) from one of my client sites where there was a big spam spike and where I was able to stop it using the “WPArmour + Cloudflare Turnstile” bundle. Can I email the data from the client site to you?
It would be nice to find a solution so that WP Armour can protect against spam again without additional solutions like Cloudflare Turnstile.
I will be grateful for your reply! Thanks!
Hi Alexander,
Thanks for taking the time to update the theme and answer my question. I have already updated the theme to version 1.1.7 and the Metabox plugin to the latest version. So far, no problems have occurred. Everything is working fine.
In addition to my own review.
I decided to support the development of the plugin through Patreon. I saw that you are on Patreon. The amount is small, but I wanted to thank you for a great anti-spam plugin.Hi Jeff,
Thank you for your update. Very glad that you liked my idea and took the time to implement it in the plugin. Your WordPress projects are a huge help to the whole community. Thank you for that!
Hello @lemouz
No. This problem is still relevant, because the developer of the Zero Spam plugin has not yet solved it. On sites where Zero Spam was installed I temporarily disabled WP Fastest Cache to avoid caching of pages, which are created by Zero Spam plugin and should be shown only to bots.Yes. I created a thread in the support forum on the Zero Spam plugin page yesterday, but no response yet. I hope that a solution will be found. For now, this problem can be marked with the status “Pending”))
Hello,
Thank you for your reply. I can observe this problem only when caching with your plugin. I have never used other caching plugins on any of my sites. Also, I’m guessing that this problem may be more to do with the WordPress Zero Spam plugin. Most likely Zero Spam conflicts with the cache plugins in some way.Hello Zeno,
I’m very glad you were able to respond. It was important to me. Thanks for the plugin and the support.
Hello,
I emailed you the diagnostic file and duplicated the previous message about the problem.
I would appreciate your response and help. Thank you!