Abigailm
Forum Replies Created
-
Forum: Plugins
In reply to: [Sky Login Redirect] Bug Report: PHP 8.0 Fatal errorThanks — I can confirm that this has eliminated the warning on my end.
Forum: Plugins
In reply to: [Sky Login Redirect] Bug Report: PHP 8.0 Fatal errorMatt, I have now tested and site function is fine.
However, I am seeing multiple PHP warnings
PHP Warning: Undefined variable $class in .../plugins/sky-login-redirect/includes/options.php on line 698PHP Warning: Undefined array key "redirect_to" in .../plugins/sky-login-redirect/sky-login-redirect.php on line 281PHP Warning: Undefined array key "HTTP_REFERER" in .../plugins/sky-login-redirect/sky-login-redirect.php on line 465Various “undefined” warnings seem to be thrown off a lot with PHP 8 — they don’t impact site function, but they do have a tendency to fill up logs. (I have tried to disable logging of these on my sites, but they still show up in my log, unfortunately)
- This reply was modified 5 years, 1 month ago by Abigailm. Reason: additional errors seen in logs
Forum: Plugins
In reply to: [Sky Login Redirect] Bug Report: PHP 8.0 Fatal errorNo — it wasn’t — I have installed it now and will test later tonight and report back. Thanks for the heads up!
Forum: Plugins
In reply to: [Quick Paypal Payments] PHP 8 coding issuesAlan,
The problem is that warnings can fill up logs on a server pretty quickly. In this case, a single instance generated 8 lines of PHP warnings. 8 lines isn’t much — but if the error is repeated on a moderately busy site over the course of a day, it’s not hard for log files to grow geometrically. I have tried to disable non-fatal error PHP warnings on my server but it just doesn’t work — they keep showing up in the logs.In my case it doesn’t matter, I can’t run PHP 8.0 on this particular site anyway, so it’s back to PHP 7.4— but I’m going to feel differently next November when active support for PHP 7.4 ends.
And PHP “warnings” ultimately turn into fatal errors as new PHP versions are pushed out. So I simply wanted to let you know because I assume you want to create clean code in the end. I’d think it would be easier to note this now before it becomes a critical problem.
Forum: Plugins
In reply to: [GAinWP Google Analytics Integration for WordPress] PHP 8@thomtra – thank you so much for posting the patched files to github. I have just begun very slowly rolling out PHP8 on some of my sites so that I can have a headstart on catching & debugging problems with themes & plugin. So I have confirmed that your changes work well.
Unfortunately, it looks like this plugin is no longer being supported, so I will probably have to migrate to a different plugin in any case — but at least you have provided a workable solution in the interim.
Forum: Plugins
In reply to: [ReOrder Posts within Categories] PHP ErrorThank you!
Forum: Plugins
In reply to: [ReOrder Posts within Categories] PHP ErrorIf you look at the log entry I posted, it specifically references this plugin as the source of the error:
PHP Warning: Illegal string offset ‘terms’ in //wp-content/plugins/reorder-post-within-categories/public/class-reorder-post-within-categories-public.php on line 130
If it helps, this error first showed up in the logs about a month ago.
Forum: Plugins
In reply to: [ReOrder Posts within Categories] PHP ErrorThe plugin seems to be functioning ok, but there are hundreds of log entries like this, just over the past month. I am reporting this because I would assume that you would want to write clean code. It seems to be tied to this section of code:
if (isset($queriedObj->taxonomy) && isset($queriedObj->term_id)) { /** @since 2.9.1 fix multi-term queries bug */ $validate = true; switch(true){ case $wp_query->is_category and ($wp_query->is_tag || $wp_query->is_tax): case $wp_query->is_tag and ($wp_query->is_category || $wp_query->is_tax): case $wp_query->is_tax and ($wp_query->is_category || $wp_query->is_tag): $validate = false; //multiple taxonomy queried. break; case isset($wp_query->tax_query): foreach($wp_query->tax_query->queries as $t){ if(is_array($t['terms']) && count($t['terms'])>1) $validate = false; //multiple terms queried. } break; } if(!$validate) return 0; $term_id = $queriedObj->term_id; $taxonomy = $queriedObj->taxonomy; // debug_msg($wp_query->tax_query->queries, "$taxonomy is ranked $term_id "); } else { return 0; }- This reply was modified 5 years, 3 months ago by Abigailm.
Forum: Plugins
In reply to: [Quick Paypal Payments] Payment form brokenThank you. I can verify that things are working on my site now with the update.
I am seeing this same problem on my site:
The default payment form after installation only shows the Payment Reference field, and the text below that field of “Amount: $0.00” (with no field)
This was reported to me today and I have submitted a separate support request with my website link & a screenshot. This problem shows up when the payment form is displayed as a widget and also in the form preview field. However, the form displays properly as a block within a page. This is a new problem — I have been using QPP for many years. I currently am using – Version 5.7.8.
Forum: Plugins
In reply to: [Data Tables Generator by Supsystic] Database ErrorWell, the problem was that nothing had been done that could be tied to plugin usage — there had been no manual updates or changes to the single table that had been created with the plugin. The problem seems to have started with the update to version 1.9.99 — but rolling back to the previous version did not resolve the problem. And since the corrupted table did not respond to any of the usual commands, it could not be repaired.
In any case, in the end I have decided I don’t need to use this plugin – so it doesn’t matter for me. But perhaps my report will help if anyone else reports a similar problem.
Forum: Plugins
In reply to: [Data Tables Generator by Supsystic] Database ErrorJust a follow-up —
I wasn’t able to drop the problem table — the “doesn’t exist” error prevented that as well.I thought I could export my table, uninstall the plugin and then reinstall it — but it turns out that the export/import features are available only in the pro version.
I only had one active table, so I ended up directly copying that table into an Excel spreadsheet, then copying it back into a WP table block. Then I uninstalled the Supsystic plugin.
I’d note that with the uninstall (deactivating and deleting), the Supsystic tables were emptied but remained in the database – so I did have to manually drop them.
So basically this problem was resolved for me by abandoning use of this particular plugin in favor of an alternate solution.
Forum: Plugins
In reply to: [Sky Login Redirect] Plugin update (3.0) breaks siteI’m not sure I understand your question — the site has a form on the front page with a login, and also a link to /wp-login.php. I’ll send more details using your contact form as suggested.
Forum: Plugins
In reply to: [Sky Login Redirect] Plugin update (3.0) breaks sitePlease disregard the note about the user being deleted — that turns out to be a different issue. However, the other function problems were real and reported by other users — when I tried to log in the page came up blank. I replicated this several times. I was able to access the dashboard by navigating to the site in a different browser tab, but then when I clicked on links from within the dashboard I also ran into the blank screen issue.
Forum: Themes and Templates
In reply to: [MyWiki] Changelog?@tony – you can see that my question was posted 4 months ago and never answered. But I did upgrade the theme. I don’t really remember details, but I probably just manually compared the specific files I was concerned about before doing the upgrade.
You can check the diff between this version and the previous version, file by file, here:
https://themes.trac.wordpress.org/changeset?old_path=mywiki/3.0.2&new_path=mywiki/3.0.3