s13_eisbaer

I ended up just setting up a new linux host instead of the crappy Windows host. Then I used a backup and restore plugin to move the site over.

Okay so I tried again to follow the instructions at https://codex.www.ads-software.com/Giving_WordPress_Its_Own_Directory#Using_a_pre-existing_subdirectory_install

This is an IIS installation so it uses web.config instead of .htaccess (I didn’t realise this the first time round).

Steps 1-3 I can’t do because the box is greyed out in general settings. So instead I opened up the wp-config.php file and updated the following code:

define('WP_HOME' , 'https://creeksideanimal.com');
define('WP_SITEURL' , 'https://creeksideanimal.com/wordpress');

Step 4. I copied (not moved) the web.config and index.php files to the root directory.

Step 5. I edited the index.php file in the root directory and updated
require( dirname( __FILE__ ) . '/wp-blog-header.php' );
to
require( dirname( __FILE__ ) . '/wordpress/wp-blog-header.php' );

Step 6. Now it doesn’t work… when I try to access the wordpress dashboard (https://creeksideanimal.com/wordpress/wp-admin/) I get the following error:

500 – Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.

And when I try to load the site at the root URL (i.e. https://creeksideanimal.com/index.php), I get the following error

Parse error: syntax error, unexpected '' ); ' (T_ENCAPSED_AND_WHITESPACE) in \\WDP\DFS\43\6\4387049060\user\sites\779069.site\www\index.php on line 17

Now, looking at that error, line 17 is the line that I updated from
require( dirname( __FILE__ ) . '/wp-blog-header.php' );
to
require( dirname( __FILE__ ) . '/wordpress/wp-blog-header.php' );
as per the instructions.

What’s going wrong?

In the box for Site address (URL): change the address to the root directory’s URL. Example: https://example.com

This box is greyed out though. So what do I do at this step?

Just realised the server this is on is IIS. That might explain why there’s no .htaccess in the wordpress directory (web.config is used instead), but strangely there is a .htaccess in the root directory for some reason.

So I just used FTP and opened the wp-config.php and found the following lines. Deleting them seems to have solved it.

define( ‘FORCE_SSL_LOGIN’, true );
define( ‘FORCE_SSL_ADMIN’, true );

Solved thanks to someone on Google+ ??

Your web host has forgotten to set up a tmp directory or to make it writable for you. If you forward the same error messages to them and mention the tmp directory they should resolve it for you.

The alternative is to override the default tmp directory by adding this line to you wp-config:

define( ‘WP_TEMP_DIR’, ABSPATH . ‘wp-content/tmp/’) ;

Then create that tmp folder in your wp-content directory and set permissions to 755. Really, though, it should be up to your host to correct.

Already tried making them 777. Didn’t work.

I’d be happy to test it out Nick. Just let me know. (www.top100experiences.com.au)

Looking forward to it ?? Just sent you something on Twitter.

Awesome, thanks ??

I’m using “Chameleon” from Elegant Themes. It’s a paid one.

Happy to give you a login for my site to have a look (and swing a donation your way:))