Patrick_D1985
Forum Replies Created
-
Ok let me get back to you guys with this;
3.06 is working fine …
4.0.0 crashes the front-end for me.So here is 3.0.6; https://downloads.wordpress.org/plugin/wp-dark-mode.3.0.6.zip
Not sure why 4.0.0 is crashing again … do hope WP Pool gets this and the closure resolved.Well, let me make that an option then; https://downloads.wordpress.org/plugin/wp-dark-mode.4.0.0.zip
Keep in mind that this is just the basic link structure for how these plugins become available. I just looked up the changelog;= 4.0.0 – 03 JAN 2023 =
- FIXED: All security issues has been resolved
- IMPROVE: Strickly followed PHPCS and WPCS as coding standard
- FIXED: Three shortcode can be used now on free version
- FIXED: Dark mode can be used on Elementor and Gutenberg block editor
= 3.0.6 – 28 DEC 2022 =
- Fixed wppool sdk missing fatal error.
- This reply was modified 3 years, 5 months ago by Patrick_D1985.
Hmm
“This plugin has been closed as of December 28, 2022 and is not available for download. This closure is temporary, pending a full review.”
That is a bit harsh, I guess WP Plugin directory did that. Not sure why as this was fixed pretty quick and I have seen way badder experience, practices etc on other plugins in the past where they did nothing at all.
Hope that gets resolved soon .But for now, could you offer a 3.0.6. link here? (Not sure if the plugin directory would allow that though, which they kinda should as it’s just bad not being able to offer a fix)
Thanks again for looking into this guys!
As a pro user I can also confirm the 3.05 base plugin critical errors multiple installs. Will revert to 3.04 as noted. But hope you can look into this as others mentioned.
@haseeb0001 trust me this comment goes a long way 😉
Just being clear about what way you are going and what happened means a lot. Thanks for that. If you go the more WooCommerce route, please keep the original an option. I for one and it seems more, really like it and will keep using it if at all possible.
Thanks again for getting back on this!
@haseeb0001 this seems fixed now.
Works without WooCommerce, Admin menu item displays again, test mail is ok.The fix is welcome and all, but more concerning is the lack of addressing the why and how this was pushed in the first place. If this was tested on anything without WooCommerce the issue would have been clear. Not addressing any user concern .. is not re-winning trust .. . which should also be happening here.
So as stated, was this overlooked, was this pushed to early … or what? Just give it some form of feedback at all besides ‘the error is fixed’. (or dont’ either way your decision, just saying it created understanding etc.)
Hi @sophiaknows I think you should check this topic out; https://wordpress.org/support/topic/mailtpl-woocommerce-email-composer-requires-woocommerce-to-be-active-to-work/
@emiubaldi totally agree, if there was any clear reason as to making such a change, an announcement, a fork of the plugin or basically whatever it would have been clear and we all would not even be here talking about it.
Not sure why they went about it like they did, but in the world of wordpress, you can have a loving support base as long as you are always transparant on why, how etc. There are enough examples in the history of wordpres where plugins, just decided to change things without prior notice or change owners and then things went a different route an all.
I’m all for calling a spade a spade, own up to everything you do .. if its bad, if its good.But if this was tested, I can not imagine this was not found out before. And sure there might have been a mixup or something … but if you see people noting all the same issue, and some even went out of their way and have looked into the code just a bit, noting having to test this on a staging site … well it is simply out of the scope of what is occuring.
Dont get me wrong I love the initial plugin for all it has done in the past and probably will continue to do in the future. But I just find it outright absurd what was pushed as an update here. So I do hope there is some form of explanation as to what happened. Because this last update experience simply put was a bad experience for probably a reasonable percentage of the install base.
As a developer, you have to earn the trust of user first to get them to use your plugin.code. And along the way people will most likely remember your missteps more then what you have done right when it comes to releases. All I’m complaining about I guess is … come clean, own up the misttake, dont sugar coat it. Because that will restore trust better then anything else.Anyway as noted hope, they can clear up what happend and / or why. And let’s hope the plugin keeps it original functionality as that has been wonderful for years.
Good to see a reply @haseeb0001 that is always appreciated.
But let’s call it what it is, as this has nothing to do with reproducing it on a staging site. The plugin literally can not function without WooCommerce with the current 1.4 release that was made available. Hence my not so frank comments earlier.
Do hope this gets resolved soon.As stated before by others, same issue.
But really what a horrendous update to push … that only seems to work with woocommerce. And I can stand by that seeing that you literally check for “manage_woocommerce” as a capability for displaying the actual admin menu item. + so much more making this for what it seems a woocommerce only plugin in th 1.4 state.
It never was that, It never was announced that it would change to that. So what where you expecting with this release except for a lot of dissatisfied and angry replies.
A lot of websites, not webshops which dont need nor want woocommerce on it now have a broken setup thanks to this mess.
Please consider fixing this and make woocommerce optional as noted by others as well. Or go the route of being woocommerce only, but then dont make this a direct update to an otherwise fine working plugin. Then just promote the now woocommerce only one in an update to the original plugin and get your specific woocommerce based customer base in such fashion.
For anyone reading; If you have this issue go here; https://wordpress.org/plugins/email-templates/advanced/ scroll down and at previous versions select 1.3.2.1 just Upload this through New Plugin in WordPress and replace.
And by all means leave the developer a message noting how screwed up this is…
Sorry guys but you called this upon yourselves.
FYI all has been resolved on my end now.
The team was informed about what to look for when it comes to WPRocket and Perfmatters.In short;
in Perfmatters;
– REST API must be set to default, as NotificationX now uses it.
– wp-data must be disabled through Script Manager everywhere (it seems to do no harm)in WPRocket;
– Load JavaScript deferred
– Delay Javascript Execution
Both need;
/wp-includes/js/dist/vendor/moment.min.js
/wp-includes/js/dist/date.min.jsThen NotificationX will work fine.
Also if you in the past added ‘notificationx’ in the mentioned WPRocket options please remove them to prevent any issues.The team might be looking into getting this solved without the above. But for now this works just fine so I am calling this resolved.
Also I got to play a bit with how flexible NotificationX now is and I like it a lot 🙂
Keep up the great work guys!Yeah policies are like that on WP.org.
No harm either way 🙂
Luckily I know what I want / don’t want te share publicly.The team reached out by mail as it is something they need some additional information for. So in short they have asked for; wp rocket config, system health details and a staging enviroment.
I have provided them currently with;
– wp-rocket config export
– perfmatters config export
(but noting that the issue is present without them (disabling them)).
– system health export
– A staging enviroment is quite a challenge as it is a big website on which we are using NotificationX.As per what I requested the team provided me with the rollback of the pro version.
So I rolled back to prior 2.0.0 on BOTH base and pro version. And the plugin is now working as it was before.As Yui explained here, if we get to resolve the issue which seems to be in the base (free) plugin. I will update this ticket, as helping one can likely mean helping many.
Once again thanks to the NotificationX team for replying and helping out in quick fashion. Thanks to Yui for keeping things clear about WP.org rules.
I’m sure the team will get this resolved 🙂
Forum: Plugins
In reply to: [upPrev] 4.0.0 issuesWeird as I really had to dig up an sql dump (which we luckily make hourly) to get my custom css and settings from there. It just seemed like the plugin got ‘reset’ to an initial config.
Anyway I got it fixed, so no worries from my end but other users might not be so handy when it comes to backups or dbs in general.
Either way, my issue is resolved, thanks again!
Forum: Plugins
In reply to: [upPrev] 4.0.0 issuesHmm I was a bit too soon.
The Upprev box is not displaying anymore it seems.It seems your config totally change :S ?
The normal options I was used to prior to 4.0.0 are all gone.
Ahhh that was all placed under advanced, that was not totally clear.Ahh it seems that it cleared the Custom Post Types I had selected….
Now it works a gain … yay!
But it killed my styles and custom css, something to checkout for sure guys as that will not make people happy 😉- This reply was modified 4 years, 10 months ago by Patrick_D1985. Reason: Also seems to have removed custom css
Forum: Plugins
In reply to: [upPrev] 4.0.0 issuesNo problem at all.
Installing 4.0.1 , now.1] Is fixed
Now displays; “Display cool, animated fly-out or fade box with related content.”2] WP CLI issue is fixed as well/
So thank you guys again for a very fast and definitive fix!
Best regards,
Patrick Dankers