Rick Radko

I’ve resolved the issue on my site. Looking at Jonathon’s plugin list with WordFence, caused iThemes Security to pop to mind, since it’s been related to redirection issues for me before. Disabling it allowed switching to work. After re-enabling, switching still worked, so I’m guessing a permalink issue that got reset?

I updated WP from 6.1.x to 6.2.2, the theme and 29 plugins. It’s an active live site, with a ton of plugins, so can’t really deactivate plugins on the site. I’d have to setup a dev site.

Hi,

I’m seeing the same issue. I just updated a site (where minutes before I had used the switch function with no issue) and I’m now getting a 500 error. It seems that there may be a error with redirects. My apache log has:

AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace.

Hi Stuart, Thank-you, that gets us back in business!

Oops, thanks. Now updated…

Hi, thank you for letting me know. I have updated the plugin to replace wp_get_sites()

• This reply was modified 7 years, 11 months ago by Rick Radko.
• This reply was modified 7 years, 11 months ago by Rick Radko.

In a post about 2 weeks ago, one of the support members in the Divi forums indicated that they will be looking at removing the code that is causing the issue as they apparently don’t need it any more.

In meantime, if anyone is looking for a patch, I posted one on Github https://github.com/r3df/r3df-popup-maker-divi-nav-fix.

Rick

Hi, I just bumped into this too. The datepicker.min.css being loaded by Gravity forms is only setting a z-index of 9999, but hits it with !important, which trumps the 2000000000 set by popup maker.

body div#ui-datepicker-div[style] {
    z-index: 9999 !important;
}

@danielmarkus, @iosios and @kopanda, this in your functions.php should patch it temporarily:

add_action( 'wp_head', 'gf_datepicker_fix', 1000000 );
function gf_datepicker_fix(){
?><style>
	body div#ui-datepicker-div[style] {
	    z-index: 2000000000 !important;
	}
</style> <?php
}

Hi, it’s fixed in the next release that I’m working on and I’ll have out by the end of the weekend.

The plugin can add a selector in the dashboard (as in the header image), as well as on the login screen, and also on the user profile.

@jahnavi27 It’s easy enough to fix in a number of ways, I just want to get it fixed in the plugin so I don’t need to maintain a patch for it on all my sites.

You shouldn’t mess with the plugin files to fix it though, it’s a bad practice. When the plugin updates you loose your changes. Create a site plugin or add it to a theme’s functions.php if you have a theme that does not update, or a child theme.

I used this to get rid of floating it to the top and to make it match the new theme.

/* admin css for user avatar */
#user-avatar-display {
    background: #888888 !important;
    left: 0 !important;
    position: relative !important;
    right: 0 !important;
    top: 0 !important;
}
#user-avatar-display h3 {
    color: #FFFFFF !important;
    text-shadow: 0 1px 0 #000000 !important;
}

I’m a developer, and seeing this issue on a site I’m working with. How do you reconnect a site without loosing the stats?

Rick

I have the problem on my local server running 5.3.8 and a prod server running 5.3.24, and version 2.2.4 of the plugin. (2.2.3 works)

I don’t think it’s a __DIR__ issue, the file
/wp-content/plugins/simplr-registration-form/lib/sreg.class.php does not exist in the install.

The message I get is:
Warning: require_once(/home/<path removed>/wp-content/plugins/simplr-registration-form/lib/sreg.class.php) [function.require-once]: failed to open stream: No such file or directory in /home/<path removed>/wp-content/plugins/simplr-registration-form/simplr_form_functions.php on line 439

Line 439 is looking for that file:
‘require_once __DIR__.’/lib/sreg.class.php’;’

I had the same problem I think, at least the dates on my events were the same. I found some entries in the wp_wpmeetup_events table in the database that had “NULL” in the “post_id” column.

Deleting those entries from the database and then doing and “Update Event Posts” in the plugin settings solved the problem.

Rick