Tony G
Forum Replies Created
-
I’m sorry – you are correct. This is the only plugin in our site that references Matomo in Composer, but yes, the plugin itself does Not use Matomo. The cookie seems to have been left over from prior testing with another plugin – I cleared all cookies and the “_pk_id” plugin associated with Matomo is no longer present.
Thanks for your patience and support.
- This reply was modified 2 years, 4 months ago by Tony G.
This is not a plugin issue. It’s related to Firefox … and it’s not even a Firefox problem, it’s an issue in FontAwesome.
Solution : Please update to FontAwesome v6.5.1
Because you can’t login to disable or update the plugin, another approach may be required. This might help:
- Login via the OS, or get FTP access.
- cd to wp-content/plugins/wp-user-frontend
- Move file wpuf.php to temp.txt (You must have permission to do so)
- Refresh any site page. This disables the plugin because it’s no longer executing.
- Now move the file back, temp.txt to wpuf.php.
- You can login now, even after step 4.
When you get in, update the plugin to v4.0.3. THEN activate it.
Don’t reinstall or you will probably lose configuration details.Good luck!
Forum: Plugins
In reply to: [Postie] Site Title with apostrophe and email SubjectI see the update. Thanks!!!
Deactivate all of my plugins to check your one-off control issue? HA!
Before copy/pasting text as though the answer might be there, how about YOU look at YOUR form and see if Excerpt has this anomaly. THEN you can suggest that the issue might be site-specific.
Try Firefox and Chrome.
Open DevTools and make sure cache is disabled.Mama Mia!
Forum: Plugins
In reply to: [Extended Post Status] Fatal Error with PHP 8.xHey bud, I flaked out on ya – have been focused on getting a site up and couldn’t take a chance with a plugin that affects post status.
I have the patch and am looking forward to doing some testing ASAP.
Thanks!
Forum: Plugins
In reply to: [User Role Editor] Do we need to keep plugin active?Perfect. Thank you VERY much for your complete response. And thank you VERY VERY much for this icon in the WordPress industry. 🙂
Got it. I’ll look into this within the next 5 days or so. Thanks!
Forum: Plugins
In reply to: [Media Sync] JPEG not showing upI just activated this plugin for the first time. Thanks!
I have hundreds of -000×000 compressed images to match thumbnails. I came here looking for that hook because it’s not in the plugin summary info. On next update, perhaps it would be good to add it?
Thanks.
Forum: Plugins
In reply to: [Extended Post Status] Fatal Error with PHP 8.xWill hit this within the next couple days. Thanks!!!
Forum: Fixing WordPress
In reply to: Synced / Reusable Patterns in a Query Loop?@sajjadakbari – Your responses are awesome. Do we compliment you on your LLM skills? 🙂 Would you share which model/prompt/database you are using to produce these great responses? It doesn’t really matter … they’re great responses. Keep posting.
Thanks.
Forum: Fixing WordPress
In reply to: Post Template deeply nested in Query LoopAlways good to get confirmation – to offset those who say it’s all in your head.
Thank you very much @sajjadakbari.
@voltronik – Thank you for your cordial response. I have to agree.
For anyone else who is concerned about these messages, they are warnings, not errors. If you disable debugging you will not see the errors anymore. As a technician of over 40 years I can’t tell you how much it pains me to say something like that, but in this case …it’s OK. Really. Let’s not sweat the small stuff. If you need the debugger active and you don’t like these warnings in your log(s), filter them out …it’s OK. Really.
To be clear, the definition of the word “deprecated” is that the feature Will, In The Future, not be supported. It does work Now. These warnings (not Errors) are for developers, to let them know they need to do something before the next release … or two … or three … or something will break Then, not Now.
I hope that helps.
Forum: Plugins
In reply to: [Extended Post Status] Fatal Error with PHP 8.xMore info: With
$term_meta=get_option(x)and get_option returningfalsewhen the option doesn’t exist, I’m guessing for now that the option"taxonomy_term_$term->term_id"doesn’t exist, so anything after that falls over. While the value not existing might seem to be impossible, it’s probably wise to check for a false value on $term_meta, report that condition delicately to the user, and report it with normal logging to the admin as an error.See /admin/class-extended-post-status-admin.php : status_meta_box_content() and elsewhere.
HTH
- This reply was modified 2 years, 6 months ago by Tony G. Reason: added detail
Forum: Plugins
In reply to: [Extended Post Status] Fatal Error with PHP 8.xI’ll make you a deal. If you can commit to publishing a fix within the next week, I’ll help to diagnose this in the new site where this occurred. I completely understand time constraints, real life, etc, so don’t bind yourself it this doesn’t fit with real life. For all we know now, some other plugin might be responsible for this and you won’t need to do anything other than that array check. If you cannot commit to addressing this, I’ll uninstall and pick up on this in a test site to give us both time to poke at it.
Thanks!