eatbuildplay

Gracias por probar ACF Engine. Visite https://acfengine.com/ para obtener documentación.

Thanks for trying ACF Engine. Please visit https://acfengine.com/ for documentation.

Thanks I did find and check those steps before but unfortunately that did not help this site. I’ve upgraded other sites to 5.5 on the same server for comparison and those work fine.

What I see on the main dashboard page under Chrome inspector, watching the network for JS files loading is that only 2 JS files load. On other sites that number is higher, at least some core JS files are not loading in the dashboard. No PHP errors, and I can see that all JS is rendered through to the closing body tag.

Those JS files that load are load-scripts.php and then wp-emoji-release.min.js.

I’ve double-checked all the core JS files are in place on the server.

I think the error message is simply incorrect – Duplicator seems to check for directories, not just “wp-config.php” file. I suspected this was the case and renamed my old WP folder to “DEL1, DEL2, DEL3”. At that point the warning flag was gone from step 1 and the install could proceed.

The block message should be updated if this is the case that Duplicator is checking for “wp-content/” and other directories.

I’m having same issue also. Tried in incognito mode, tried blocking cache with Chrome dev tools, still Duplicator seems to believe there is a wp-config.php in the folder… I definitely deleted it, and there is just no way to use the Duplicator plugin at this point.

So you have no plans to change the poor coding practices used in Ultimate Member?

As an example of a fix for the above overkill style:

.um-directory .um-search-line {}

This is already specific enough to target the search input in question because you are after all building the core plugin, so you’re only competing for specificity with other WP plugins at this level, how many of them will ever use “.um-directory”. Absolutely zero, so 2 selectors is enough to specify the target. 3+ is overkill and simply adds to the bulk of the stylesheet and then creates a real challenge in overriding styles. Here is how I had to specify more padding recently on a project with UM.

Note the use of !important, utilized only because even after I used about 8 selectors to override default styles, you’re poor practice of using !important meant I also had to use the same poor practice.

body .um-directory .um-member-directory-header .um-member-directory-header-row .um-member-directory-search-line label .um-search-line {
padding: 10px 0 10px 0 !important;
}

Now how would this look if we used sensible style specificity? Well more like:

.my-um-page-template .um-directory .um-search-line {
padding: 10px 0 10px 0;
}