benfreke

You need to change the line to this actually:

if ( isset($_POST['action']) && $_POST['action'] == 'update' && isset($_POST['twinesocial_noncename']) && wp_verify_nonce( $_POST['twinesocial_noncename'], plugin_basename( __FILE__ ) ) ) {

The nonce throws an error is you don’t check the post value is set first in some cases.

While we’re at it, you could also remove the closing php tag on line 196 ??

Thanks for pushing the fixes so quickly!

It was caused by this bug. https://core.trac.www.ads-software.com/ticket/15256

Fixed in 3.8.

The root .htaccess will be hit first, so that will definitely be interfering with thee sub-folder. Rename it and see if the sub folder starts to work.

As for wp-config, if you’re renaming the site-url in there that might interfere with anything else you’re doing in the database. It’s been a long time since I’ve used those values, but I’m pretty certain that somewhere in the init script those values will over-rdie anything you have in the database.

This isn’t an issue I’ve ever had, so I’m just trying to think of the basic trouble shooting I’d do, and hope that it helps. I’m 99% certain your issue is with the root install htaccess file though.

Hmm. If it can’t find it then you’ve uploaded it to the wrong folder (unlikely), or there is a .htaccess rule getting in the way.

Re-reading this thread, do you still have a full wordpress install on the root, along with one in sub-folder /dev? I suspect that if you do, that the root install of wordpress is interfering. That’d be my first guess.

My second guess would be that the copy to the sub-directory went wrong somewhere, or there are conflicting rules somewhere in wp-config or similar where you’ve tried to fix things.

If my first guess doesn’t work, I think you could save a lot of time and effort by starting from scratch with the instructions you followed the first time. It doesn’t look like there will be a quick fix for this one sorry.

Hi

Your server has encountered an error, and stopped processing code. If you view the source, you can see that the last line of html is

<div class=”content_full_width”>

You will need to look at your error log, or enable WP_DEBUG in your config to get more information. There is something different in the server configuration of those two servers that is causing the issue.

Is the video that is on the homepage part of the content, and using the default wordpress embed code?

I always use a php script called searchreplacedb2. Basically it will go through your site and replace strings of text, which is how WordPress stores everything.

Normally I use it when moving a site to another server, so replacing example.ben.dev with example.com through out the site.

In your case, it would be finding “example.com/wp-content” and replacing with “example.com/dev/wp-content”.

The advantage of this script is it will definitely update any serialised strings, which the existing plugin might be skipping.