crazywhistlepig

marked as resolved, is there a solution?

Thank you!

Hey @mialewp,

I have a photography heavy web site and just want to organize files in my media library like I did with WP Media Folder. Dont care about front end visibility would just like to organize my media in folders and have them available when choosing media for my Elementor posts/pages. I saw herein that people are having PHP 8.2 issues, and just wanted to check compatibility before I purchase the pro version. So far the lite version works withouyt errors, but I do not have all options available in the lite version for testing. Also is it possible to import folders from WP Media Folders?

Just wanted to leave a comment for PHP 8.2 support. Just updated my server and 8.2 is the default. I’d love to buy this plugin, the lite version 5.6.0 hasnt thrown any errors for me yet but doesnt quite meet my needs.

I know this is an old thread, but thought I’d post my solution in case it helps anyone.

I had a similar issue. Scoured the code, the database, and could find no real offenders. Insecure urls in namespaces like in the XML or SVG headers should not matter. I even ran the replace URL tool and rebuilt the CSS caches. Still had SSL errors.

My solution, was to replace the background images in all sections with a background image attached. Not sure how Elementor stores these urls, maybe encoded or in a serialized string, but they are not readily found in the database or by using Elementor’s own find/replace tools.

My exact procedure was to go to each background image in EDIT SECTION > STYLE > BACKGROUND, and choose a new image (for simplicity I just chose a temporary neighboring image). After the image was replaced I went back and replaced it with the orginal image. After doing that for EVERY section with a background image, my SSL is locked and I have no more mixed use errors.

My lesson learned here, install the SSL cert FIRST! ??

• This reply was modified 4 years, 7 months ago by crazywhistlepig.
• This reply was modified 4 years, 7 months ago by crazywhistlepig. Reason: Edited for clarity

Very sorry for the super late reply, but yes that appeared to have fixed that issue along with another where the justified galleries that have a thumbnail link of “not linked” were having the justification and row height broken and displaying simply inline-block full size thumbnails. Thanks for the update!

I just had a similar issue and spent the last few days trying to track it down. I was getting many LimitInternalRecursion errors and 500 errors. Seems that after a multisite move (and to a newer version of WordPress) the /wp-content/blogs.dir/ folder changed to /wp-content/uploads/sites/.

Any image search engine link (from Bing for example) that pointed to the old /blogs.dir/999/someimage.jpg was getting a recursion loop then a 500 error. The recursion loop happened due to the fact I did not have any global 404 errordocuments defined in Apache. The direct link to /wp-content/blogs.dir/ occurred outside of the WordPress rewrite scope (default wordress 404 mechanism) and with no errordocs, was causing a loop which ended in a 500 error. The loop also flooded my logs with LimitInternalRecursion errors.

My solution, since I wasn’t about to create redirects for over 100 sites, was to do a soft 404 in my multisite .htaccess file (above the wordpress section) to anything going to blogs.dir like so:

ReWriteRule ^wp-content/blogs\.dir/.*$ / [L,R=404]

This redirected any image links going to blogs.dir to the site home page with a soft 404 to alert the referrer of the missing file. I thought about doing a rewrite on the folders, but in my migration, blog_ids changed as well as some image names so it would be cumbersome to say the least. Plus those deprecated links should be removed and new images indexed IMO.

Since your issue doesn’t seem image related like mine, your solution may be in just verifying you have the proper Apache errorpages in place (not your theme error pages).

Hope this helps or at least points you in some direction to a solution!

Woocommerce. I just migrated all of my Web sites to Woocommerce from Shopp.

The reason? I purchased a developers license for Shopp a few years back which was to entitle me to lifetime free updates and support. However, Shopp did not see it that way and revoked the ability to receive free updates and support without grandfathering us in. A real bummer since I paid $299 for the developer license vs. $75. They were even going to revoke our developer forum access leaving us all out in the cold but after many complaints and threats of lawsuits they at least allowed continued access. Its bogus and a shame because I thought it was a great plugin, the support at the time was decent, and the built in help videos were awesome.

But after a few years Woocommerce has really caught up and is probably the best (locally hosted) cart plugin for WordPress. Theres also a tremendous amount of 3rd party plugins extending Woocommerce’s functionality out there.

That being said Ive never interacted with Woocommerce support, I’ve never needed to, so I can’t vouch for it’s quality or efficiency. However, once you start using it, you begin to notice its used everywhere out there. Also, you’ll find a lot more resources out there when Googling your Woocommerce support issues because they have pretty extensive online documentation and do not covet their support resources like Shopp does.

Thanks! I do have a multisite test environment and would be happy to help further if needed.

So to do that, I have to create a different term on the subsite. E.g.:

mainsite.com/?termA=1
sub.mainsite.com/?termB=1

However, the plugin only writes the latest change to .htaccess, negating the prior site’s cookie. If I backup the .htaccess file and combine the rewrite directives I can get it to work, however this is not ideal or convenient, especially with over 30 sub sites.

I also have to set the WordPress MU Domain Mapping plugin to disable primary domain check if I want to be able to use the edit links from the front end of the current theme.

I’m eager to try this method of brute force protection, seems like it will work very well. Redirecting to 127.0.0.1 is brilliant!

Thanks!

I’m having the same issues. Question is why is WordPress trying to scrub my $_POST ? This is just about as retarded as its built in stripslashes.

EDIT:

Had to do this to get the widget to render properly. Since the actions echo by default, I created a filter instead and buffered the output.

/* Add menu items to the PreHeader menu */
function my_menu_items($items, $args) {
    if( $args->theme_location == 'preheader' ){
		$items .= '<li><a class="dropup-link" href="#">More</a>'.apply_filters('my_filter').'</li>';
		$items .= '<li><a href="#">Customer Login</a></li>';
    }
    return $items;
}
add_filter( 'wp_nav_menu_items', 'my_menu_items', 10, 2 );

/* Add widgets to your theme (if you haven't already) */

/* Define extra widget areas */
function my_widgets_init() {
    register_sidebar(array(
       	'name' => 'Navbar',
       	'id' => 'navbar-widget',
       	'before_widget' => '',
       	'after_widget' => "",
	'before_title' => '',
	'after_title' => "",
    ));
}
add_action( 'init', 'my_widgets_init' );

/* Adding the navbar widget */
function my_navbar_widget() {
      if (function_exists('dynamic_sidebar')) {
	ob_start();
	dynamic_sidebar('navbar-widget');
	$out = ob_get_clean();
	return $out;
      }
}
add_filter('my_filter', my_navbar_widget', 8);

Seems to work so far.

HA! I just used your question to solve my own code dilemna so thank YOU! The least I could do is post my solution. Here’s a full example:

/* Changes to your example */

/* Add menu items to the PreHeader menu */
function my_menu_items($items, $args) {
    if( $args->theme_location == 'preheader' ){
		$items .= '<li><a class="dropup-link" href="#">More</a>'.do_action('my_widget_action').'</li>';
		$items .= '<li><a href="#">Customer Login</a></li>';
    }
    return $items;
}
add_filter( 'wp_nav_menu_items', 'my_menu_items', 10, 2 );

/* Add widgets to your theme (if you haven't already) */

/* Define extra widget areas */
function my_widgets_init() {
    register_sidebar(array(
       	'name' => 'Navbar',
       	'id' => 'navbar-widget',
       	'before_widget' => '',
       	'after_widget' => "",
	'before_title' => '',
	'after_title' => "",
    ));
}
add_action( 'init', 'my_widgets_init' );

/* Add the navbar widget */
function my_navbar_widget() {
      if (function_exists('dynamic_sidebar')) {
	dynamic_sidebar('navbar-widget');
      }
}
add_action('my_widget_action', 'my_navbar_widget', 8);

Hope it makes sense.

I have 42 sites in a multisite environment, and I have the lockdown table for sites 1 and 2 and thats it. It stopped being created after that. My error_logs are also filling up with these errors. Deactivating and reactivating did nothing, btw.

I was getting these errors on both the frontend and backend of the site after upgrading to 6.2.3:

Warning: reset() expects parameter 1 to be array, null given in /<path>/wp-content/plugins/theme-my-login/modules/themed-profiles/themed-profiles.php on line 230

Fatal error: Call to a member function get_page_permastruct() on a non-object in /<path>/wp-content/plugins/theme-my-login/includes/class-theme-my-login.php on line 491

Upgraded to 6.3.3 and the errors are gone and so far looks to be functioning as expected. Login/logout work. I’m also using Ultimate Branding by WPMUDev.org and all seems okay.