Patrick_D1985
Forum Replies Created
-
Forum: Plugins
In reply to: [Wordfence Login Security] Why sunset a well used plugin?Like frankly all of the above people have noted, Wordfence Login Security is something I would and do run on every possible install. Wordfence Security the main plugin is not.
And that all boils down to;
WFLS is lightweight, Wordfence main in all essence simply is not.
WFLS has been tested and working in countless situations, Wordfence main has always had a love/hate relationship with multiple plugins/setups.
And dont get any of us wrong here we for sure love the current offering WLFS does, look at the 70K+ installs, it’s a testament you have something great there, why abandon that?
If this sunset does go through, I hope someone forks this and can maintain it with security updates.
If that is not the case, which I dont hope, for me and all installs I handle that means goodbye Wordfence all together.Please reconsider.
Hi @danielmanzau sorry for my late reply, it’s been a busy week.
Sorry to hear you are running into something similar. As far as I can recall I got this resolved with a testing version provided by the team and later on base 6.24. Haven’t had those issues since.
If you are running into something similar, it’s best as support moderators guidelines say that to create another topic detailing your exact issue (I did not make those rules up… but hey they are the guidelines and let’s prevent you from having to deal with that stuff)
Best regards,
PatrickAnyway resolved, consider this closed.
I am well aware of the guidelines, hence my clear reference of where the issue lies. (the base version of the plugin, the same plugin available on the public WordPress plugin directory). If we can’t address an issue with the latest public version of the base plugin has here … what good is this entire support forum at all? Really I get I can’t ask for pro support on the pro plugin here, but that is not at all what I am doing.
If you would have read my reply just a bit more closely, you would have seen I am a legacy customer, with no active support subscription to the pro version. (Shall I once again point out … it has nothing to do with the pro version?) Hence as that route is probably going to be a can of worms and repetition (and where it has nothing to do with the pro version), I replied here, simply asking if that is ok to the devs.
Then getting shot down like that by moderation is just plain weird. Don’t talk about the free version here …goes so against anything the support forum stands for :S what should we discuss here then? The weather? Politics?
Sure I will reach out as noted as I am a free and (legacy) paid user. (keep in mind I have an issue with the free version only, never did I once note I had an issue with the pro version, which in my eyes still clearly means; discuss it on the public WordPress plugin directory support forum for said plugin)Confusing stuff these support forums nowadays…
Sure but the reason I reached out here is, that it’s a issue with the BASE plugin. As you can see “/plugins/formidable/formidable.php” is throwing the error, if I switch the base version back to 6.22.3 the issue is gone.
Also I am one of the users with a grandfathered license which notes;
Grandfathered Licenses
Your grandfathered license gives you access to Formidable Forms updates for life. It is not eligible for renewal or upgrade. A new license will be required to get access to more features and support.Which I have not kept up to date as I never needed support for the Pro version.
SO, first of, I get your request, but for an issue with the BASE plugin should I still reach out to the team by mail, and will they even look at given the status of my PRO grandfathered license?
And all of the above is why I am cancelling my Pro license with them. It worked nicely but I’ll revert to a custom solution for what it does. The Patchstack reply was the final straw to make me take that decision. when you are informed and do nothing for so long .. well that speaks volumes.
Forum: Plugins
In reply to: [Comments - wpDiscuz] wpdiscuz.com – This site can’t be reachedAh great to hear guys 🙂
Forum: Plugins
In reply to: [Comments - wpDiscuz] wpdiscuz.com – This site can’t be reachedHi there,
Just to confirm; Seems down from all angles (tried various urls) as it now serves a 503 – Service unavailable.
The company website of gVectors (the team behind WPDiscuz) is up though. See; https://gvectors.com/
Perhaps they are testing something on wpdiscuz.com
EDIT:
Hmm this is weird though; the WordPress plugin notes;
AdvancedCoding
@advancedcoding on WordPress.org
Member Since:April 23rd, 2014
As the author of this plugin …. see; https://wordpress.org/plugins/wpdiscuz/
So either, new ownership, or something fishy. Or was this always their handle, im not sure.
Hope that gets cleared up soon.- This reply was modified 1 year, 1 month ago by Patrick_D1985.
- This reply was modified 1 year, 1 month ago by Patrick_D1985. Reason: Author handle throws me off
Forum: Plugins
In reply to: [Comments Engine AI] Bulk action Generate CommentsHi Alexandre,
Great looking forward to it.Best regards,
PatrickForum: Plugins
In reply to: [Comments Engine AI] Bulk action Generate CommentsAwesome Alexandre 🙂 thanks for looking into this!
I did see the bulk actions show for the media library, but I can imagine some people allow comments on Attachments. Also saw it get shown for Formidable Forms.
Just thinking out loud here, would it be cumbersome to add list of all registered Post Types with checkboxes in the settings of the plugin (perhaps when clicking on Additional) so each customer can determine for themselves they need actually it? (and defaultl just enable it on every post type)
Sorry to be a pain, but giving users control over that keeps their UI as strict as they want.Once again, thanks for being awesome!
Best regards,
PatrickForum: Plugins
In reply to: [Da Reactions] Admin Ajax speed + Xdebug parameterHi Daniele, thanks for getting back on this.
Yeah SHORTINIT can be a bit of a pain to get the current user. There are some ways to do this but I’ll leave that on the table if those are good ways of doing so (JS or other methods of storing the current user id for example) . And if response times remain more or less equal beyond that well then the gain of doing that is well unneeded. I was just wondering if there was something to be gained on this end.
In regard to the wp_cache transition, speeds seems a bit better, on my larger install it takes roughly 1-1,5 s which is not bad at all.
Ah cool to hear about the future updates coming as well, keep up the great job!
Forum: Plugins
In reply to: [Da Reactions] Nonce error on shortcodeHi there Daniele,
Yeah I was able to test it myself a minute ago, and once the nonce check was gone the issue is gone.
Thanks being swift about this, very very much appreciated for sure.Keep up being awesome!
Forum: Plugins
In reply to: [Da Reactions] Nonce error on shortcodeHi Daniele,
Thanks for getting back to me 🙂 much appreciated!
Disabling cache for the shortcode, would not even know how to make that happen. (Beside some hacky ways, which you shouldnt do hahaha)
And for the specific page it a bit hard, as I do use it on more or less on every CPT except “page”.
I’ll give the other workaround a chance later on and report back.Best regards and thanks again!
Forum: Plugins
In reply to: [Da Reactions] Admin Ajax speed + Xdebug parameterHi Daniele,
Thanks for getting back to me 🙂
1 – Crystal clear, it happens 🙂
2 – Very cool, I think it can be doable for DaReactions and that will greatly speed it up, which for community usage (as it is for me) will be wonderful.
If I can help in any way feel free to let me know.
And keep up being awesome man 🙂Forum: Plugins
In reply to: [Da Reactions] Admin Ajax speed + Xdebug parameterOk let me correct the second point. It seemed another plugin was wreaking havoc to weirdly only some admin-ajax calls. Finally found out who the culprit was today; ‘Simple Link Directory Pro’ which was also causing a slowdown in our backend. We only use it for our “We support listings” but will be dropping that one … as that behavior is way out of line.
Admin-ajax calls seems to take max 1.5-2 seconds now including DaReactions 🙂
The first point, im still interested as into why the XDEBUG param.
And If you want we could discuss if a SHORTINIT ajax call for DaReactions can be something (that could still speed the calls up quite a bit as you could bypass a lot of WP.
Best regards,
Patrick