LazyLeopard
Forum Replies Created
-
Forum: Plugins
In reply to: [Sky Login Redirect] No longer re-directing usefullyThanks. It’s working again. 🙂
Forum: Plugins
In reply to: [Membership Plugin - Kadence Memberships] Just Updated, Broke SiteThis morning I have just had to repeat the action I described a few months ago, deleting everything after line 994 in restrictcontent.php to get my site back working again.
This version seemed OK –> 32924 Jul 25 09:39 restrictcontent.php
That block of code at the end of restrictcontent.php even breaks the WP admin pages….
- This reply was modified 1 year, 6 months ago by LazyLeopard. Reason: Adding information
- This reply was modified 1 year, 6 months ago by LazyLeopard.
Forum: Plugins
In reply to: [Membership Plugin - Kadence Memberships] Just Updated, Broke SiteProblem is a sales banner they’ve added to wp-content/plugins/restrict-content/restrictcontent.php
Go to theend of the file (around line 1000) and delete everything after the line that reads:
add_action(‘admin_notices’, ‘restrict_content_bfcm_notice’);
(Keep that line. Delete all that follows.)
That got my site back up and running…
The change kil0p suggests above does seem to fix the problem and enable the function to be restored. Thanks.
Indeed it doesn’t (using version 3.6.5 with WP 3.8.1) …
Anyone who hasn’t yet moved up from 3.6.3 should consider staying there…
Use:
http://your-site-name-here/wp-login.php?your-secret-hereMine isn’t. The login links point to a page something like this:
http://site-host-here/wp-login.php?redirect_to=http%3A%2F%2Fsite-host-here%2F
…which then re-directs to:
http://site-host-here/not_found?redirect_to=http%3A%2F%2Fsite-host-here%2F
rather than the appropriate wp-login page.
I can login using the appropriate wp-login link, thanks to having a record of the “secret” key…
(Oh, and I’ve tried again several times, way past the 30 minutes or so mentioned above.)
Apologies. I just re-installed EM 5.4.4 on the test server on which I spotted the problem with EM 5.5, and EM 5.4.4 gives the same error. The test server has more verbose error reporting than the production server, it seems…
Theme, if it makes any difference, is ‘Weaver II’.
With EM 5.4.4 and EM 5.5 the same message is produced if I switch to Twenty Thirteen. I don’t have Twenty Eleven or Twenty Twelve installed any more to test them.
Happens with EM 5.5 when you try to display a single event category. Did not happen with EM 5.4.4.
Warning: Creating default object from empty value in …/wp-content/plugins/events-manager/classes/em-category-taxonomy.php on line 22
Settings>Pages>Event Categories are:
Categories page (a page with a parent, and just ‘CONTENTS’ in page body)
Override with formats: Yes
Default archive ordering: Order by start date, start time AscendingDefault list ordering: Order by name Ascending
List Limits 12
Event List Limits 20Rather oddly, I have this problem in one of three copies of a site I’m testing. They’re on different servers, so I’m busy trying to determine whether there are any server settings that might cause one to throw the warning while the other two do not. (Edit: Yes, the server showing the message is set to display errors, and the others were not. The warning is displayed on all three now that I’ve alogned their settings more closely.)
I do have a plugin active that adds custom attributes to posts, including custom post types like events and locations, and initially I wondered whether the non-EM custom attributes were giving EM a problem…