kyleboreing

I am having the exact same issue.

I am also attempting to do this for local testing, but am running into the same problem. I have split the install with core files going to a folder marked ‘web’ and wp-content in a folder marked ‘data’. Here is the code I’ve inserted to try to get the themes/plugins to display in the new folder location:

define( 'WP_CONTENT_DIR', dirname(__FILE__) . '/wp454split/data/wp-content' );
define( 'WP_CONTENT_URL', 'https://localhost:8888/wp454split/data/wp-content' );
define( 'WP_PLUGIN_DIR', dirname(__FILE__) . '/wp454split/data/wp-content/plugins' );
define( 'WP_PLUGIN_URL', 'https://localhost:8888/wp454split/data/wp-content/plugins' );
define( 'PLUGINDIR', dirname(__FILE__) . '/wp454split/data/wp-content/plugins' );

I’ve tried varitions with and without ‘wp454split’ in the path, with and without the full URL, and I still am getting the same exact error. This has been happening since WP 4.4. Was there an update to the framework that would’ve made this more difficult?

Anyone have any info??

Yes, just above “That’s all….”

I fixed the problem….had to change “https://” to “https://” in the back-end.

We are having the same issue. All other embeds are working properly, but I think YouTube may have changed some of their embed settings, rending this plugin inoperable in its current format….any others having a similar issue?

You’re not the only one. My understanding is that the TinyMCE plugin was overhauled with the latest update, which has eliminated much of the table tools.

On top of that, there appears to be a glitch wherein the latest update does not detect a current WordPress installation.

The Permalinks are set properly. I do have one question/observation…

What files/directory does this command refer to? The reason I ask is because our core and content files are in separate directories – the wp-content directory not in the same folder as the wp-admin directory for deployment purposes. Could this be part of the issue? And if so, is there a workaround for this?

I have defined this constant in our local testing environment, which worked fine, but when I attempt to deploy it to our internal QA server, it keeps returning a 404 error. I’ve tried it several times, and each time gives the same problem. Any ideas why this might be the case?