greatpages

No worries and no pressure.
Issue on my side/site was already resolved with a little bit of CSS.
Saw the update yesterday and also updated to the recent version. To be able to provide you with the correct feedback I commented out my code and rolled back to the previous state.
And what can I say? It seems the issue is resolved. ??
I’m really impressed with the effort you and the team put into this. Really appreciated! Please make sure to let them know and pass on my thanks to each of them.

Feel free to close the ticket.
Wish you all the best,

-Bj?rn

Hello Tarek,

appreciate your reply.
A little detail I forgot to mention in my previous post:
This issue only occurs when you disable the first line of the table to be the header, otherwise you probably wouldn’t notice.

Best regards,
Bj?rn

UPDATE:
In a live environment using PHP 8.0 folder sync is working fine.
I’ll leave it at this point as I already spent way too much time on this.

Thanks for the exchange anyways! Best regards,

-Bj?rn

Hello Peter,

thank you for your thoughts on this.
Might be possible that the issue is located within XAMPP. Am not convinced yet, but my interest is triggered. Will set up a live environment today to dig deeper into this. Keep you posted.

EDIT:
While preparing the installation I kept on reading on issues regarding PHP 8 and WordPress.
In this interesting article I stumbled upon the possibility of a misconfiguration causing a fatal error, which is having strict type checking enabled.
https://make.www.ads-software.com/core/2020/11/23/wordpress-and-php-8-0/
To me this is currently the most likely reason for my issues.
Going to investigate in a fresh XAMPP environment as well.

Thanks so far, best regards

-Bj?rn

• This reply was modified 1 year, 9 months ago by greatpages.

LATEST UPDATE:
I’m done for today.

Tested with PHP 8.0.5, 8.0.0 and just to make sure with 7.4. All tests have been performed under same conditions (settings, themes and plugins).
Error stopped occuring with the latter (7.4).
Now I’m more curious to know how you managed to sync folders running PHP 8 than getting this issue resolved. Which browser are you using most of your time? And which version is it?

Best regards,

-Bj?rn

UPDATE:
Now that’s mysterious…

Uninstalled everything, including deleting registry, browser cache, wordpress files & db.
Re-installed and set up new instance now running on PHP 8.0.8, because that seemed to be the version you were still able to sync folders with.
But unfortunately the error is still occuring. Same error message, thrown in C:\xampp\htdocs\my-page.de\wp-content\plugins\media-library-plus\media-library-plus.php on line 3124.
Even increased max_execution_time to 300 as suggested in your FAQ, but without any success.

Will try even fewer releases of PHP now.

Best regards,

-Bj?rn

• This reply was modified 1 year, 9 months ago by greatpages.

Don’t feel bothered by me, just wanted to give you a short feedback.

Got rid of the complete development environment including WordPress and db.
Now I’m running WordPress 6.1.1. on PHP 8.0.25. Media Library Folders is installed with version 8.0.6 and the file “Folder_to_Hide.txt” also exists in the plugin’s root folder.
Browser cache has been deleted within the process of uninstalling and setting up the new environment.
Permissions to all files and folders are given.
Unfortunately I’m getting the exact same error at the exact same point (while trying to sync folder content).

Already tried resetting folder settings, but without success, the error message keeps coming up.

[Thu Feb 23 23:47:04.248167 2023] [php:error] [pid 1612:tid 1836] [client ::1:51371] PHP Fatal error: Uncaught ValueError: Path cannot be empty in C:\xampp\htdocs\my-page.de\wp-content\plugins\media-library-plus\media-library-plus.php:3124\nStack trace:\n#0 C:\xampp\htdocs\my-page.de\wp-content\plugins\media-library-plus\media-library-plus.php(3124): file_get_contents(”)\n#1 C:\xampp\htdocs\my-page.de\wp-content\plugins\media-library-plus\media-library-plus.php(4738): MGMediaLibraryFolders->max_sync_contents(’15’)\n#2 C:\xampp\htdocs\my-page.de\wp-includes\class-wp-hook.php(308): MGMediaLibraryFolders->mlfp_run_sync_process(”)\n#3 C:\xampp\htdocs\my-page.de\wp-includes\class-wp-hook.php(332): WP_Hook->apply_filters(”, Array)\n#4 C:\xampp\htdocs\my-page.de\wp-includes\plugin.php(517): WP_Hook->do_action(Array)\n#5 C:\xampp\htdocs\my-page.de\wp-admin\admin-ajax.php(188): do_action(‘wp_ajax_mlfp_ru…’)\n#6 {main}\n thrown in C:\xampp\htdocs\my-page.de\wp-content\plugins\media-library-plus\media-library-plus.php on line 3124, referer: https://localhost/my-page.de/wp-admin/admin.php?page=mlf-folders8

Best regards,

-Bj?rn

Will do. ??
Thanks for you looking into it.

Best regards,

-Bj?rn

Hi Alan,

thank you for the fast reply.
I can confirm both of your questions. Version 8.0.5 of Media Library Folders is installed and the file Folders_to_hide.txt is in the path you mentioned.
Only difference is the PHP version that I’m currently running, which is 8.1.12 in my case.
WordPress is up to date as well.
Developing locally on my machine I’m using XAMPP to provide the required server environment.

Already disabled all other plugins, checked server settings, deleted browser cache and tried again, but always with the same result. Tested on latest Chrome and Firefox browsers.
Aside from the developer tools in Chrome the browser is also giving an error message, but it’s more than general and isn’t giving any details:
“There was a critical error on your webpage. Learn more about troubleshooting within WordPress.”

The last time I was facing this issue I went back to PHP 7.4 and everything worked like a charm again.

If there’s anything else you would want me to look into, let me know and I’ll happily assist.

Best regards,

-Bj?rn

UPDATE:
Switched back to PHP 7.4 and made same config changes as to PHP 8.
Created new database and installed a fresh WordPress version to localhost.
Installed MLF plugin and synced folder content without any issues. ??

Although I made a thorough research I wasn’t able to find any specific setting I should have made for PHP 8 to resolve the issue from my previous post. But I stumbled upon a bunch of error reports regarding other plugins that seem to have similar issues.

For everybody who’s interested to know how to add sticky and shrink on scroll effect to the Storefront header and top-bar-plugin.
These are the instances that you need to add the “shrink” class to:
.site-branding
.search-field
form.woocommerce-product-search
.site-header
.site-content
The code goes into your function.php:

add_action ('wp_footer','create_shrink_class',1);
function create_shrink_class() {
?>
<script>
jQuery(document).ready(function($) {
    $(window).scroll(function () {
        if ($(window).scrollTop() > 400) {
			$('.site-branding').addClass('shrink');
			$('.custom_content').addClass('shrink');
			$('.search-field').addClass('shrink');
			$('form.woocommerce-product-search').addClass('shrink');
			$('.site-header').addClass('shrink');
			$('.site-content').addClass('shrink');
        }
        else{
			$('.site-branding').removeClass('shrink');
			$('.custom_content').removeClass('shrink');
			$('.search-field').removeClass('shrink');
			$('form.woocommerce-product-search').removeClass('shrink');
			$('.site-header').removeClass('shrink');
			$('.site-content').removeClass('shrink');
        }
    });
});
</script>

<?php 
}

All that’s left is adding the proportions and positions you want these items to have before and after shrinking. For example this is the CSS for the magnifying glass:

/*DEFAULT SEARCH ICON*/
form.woocommerce-product-search::before {
	top: 1em;
	transition: 0.8s ease-in-out;
  -moz-transition: 0.8s ease-in-out;
  -webkit-transition: 0.8s ease-in-out;
  -o-transition: 0.8s ease-in-out;
}
/*SEARCH ICON SHRINK*/
form.woocommerce-product-search.shrink::before {
	top: 0.4em;
	transition: 0.8s ease-in-out;
  -moz-transition: 0.8s ease-in-out;
  -webkit-transition: 0.8s ease-in-out;
  -o-transition: 0.8s ease-in-out;
}

According to your top-bar’s height and your final header height you need to repeat these steps for each item.
One thing I still need to implement are media breakpoints for the top padding of the main content. Due to the header being responsive fixed positions might give the result a different look on different sized screens.
For future readers: You should be able to see the final results on https://www.andarilorell.de

Can’t end this day like that. ??
Full code:

section.woa-top-bar.col-1.fix {
	position: fixed;
	top: 0;
	width: 100%;
	z-index: 9999;
	background: #ffffff;
}
#masthead {
	width: 100%;
	margin-top: 37px;
	position:fixed
}
#content.site-content {
	margin-top: 154px;
}

I’ll add shrink on scroll effect to both parts (header + top bar) tomorrow and would post it here. Just in case it might be helpful for others.

Best regards,

-Bj?rn

Just realized the site-content is moving up this way. Too late for now, I’ll post an update tomorrow.

OMG – YOU are awesome! ??
Your solution is close to my exact approach. WITH one important difference. As soon as I added the z-index, everything became clear to me.
Here’s my full code before:

#masthead {
	position: fixed;
	width: 100%;
	margin-top: 37px;
}
section.woa-top-bar.col-1.fix {
	position: fixed;
	top: 0;
}

After your response I tried with the z-index first. Seeing the outcome put me immediately in a condition of shame…still lasting. ??
Here is the complete code I’m using now:

#masthead {
	position: fixed;
	width: 100%;
	margin-top: 37px;
}
section.woa-top-bar.col-1.fix {
	position: fixed;
	top: 0;
	width: 100%;
	z-index: 9999;
	background: #ffffff;
}

I guess this is a step forward for not just me. As I saw after opening this thread, your plugin description still carries the note that it does not support the sticky header option: https://www.ads-software.com/plugins/storefront-top-bar/
Oh and yes, I am using the storefront theme. This thread should be the proof sticky header + top bar is fully working now. ??

Thanks again for your help! You saved me a lot of time. All the best,

-Bj?rn

UPDATE 2:
Sometimes a little distance is helpful to get a different point of view. Just realized that I already reached my goal. Only thing left now is unhooking secondary navigation menu and hook it above header.

Best regards,
-Bj?rn