Path issues

Resolved MicF
(@micf)

9 years, 9 months ago
Hi,

I’ve got a problem setting Sitepush up.
I get a warning, when saving the options:
Warning: Currently configured WordPress uploads directory (/homepages/37/d428665981/htdocs/bs/wp-content/uploads) is different from the configured uploads directory in your sites config file (/homepages/37/d428665981/htdocs/bs//wp-content/uploads)

I suspect, it’s the double slash, that makes the problem. But WP_Home and WP_Siteurl are set, correctly:
```
define('WP_SITEURL', 'http://www.bs-fdl.de/bs');
define('WP_HOME', 'http://www.bs-fdl.de');
```
The site config is set like this:
```
[all]
wp_dir = /
wp_content_dir = /wp-content
cache = no
caches[] = /caches/timthumb
caches[] = /caches/something_else

[live]
label = Live Site
domains[] = bs-fdl.de
domains[] = bs-fdl.de
web_path = /homepages/37/d428665981/htdocs/bs
db = live
live = yes

[staging]
label = Staging Site
domain = staging.bs-fdl.de
web_path = /homepages/37/d428665981/htdocs/staging
db = staging
live = no
```
Any idea?

Mic

https://wordpress.org/plugins/sitepush/

Viewing 5 replies - 1 through 5 (of 5 total)

Thread Starter

(@micf)

Interesting:

When adding a slash behind the domain path.
I get a double slash for wp-config and a triple slash for those with a subdirectory.
Omitting the slash wp-content is right, but I get a double slash to the others with a subdirectory.

SitePush Options
Warning: Currently configured WordPress content directory (/homepages/37/d428665981/htdocs/bs/wp-content) is different from the configured uploads directory in your sites config file (/homepages/37/d428665981/htdocs/bs//wp-content)
Warning: Currently configured WordPress uploads directory (/homepages/37/d428665981/htdocs/bs/wp-content/uploads) is different from the configured uploads directory in your sites config file (/homepages/37/d428665981/htdocs/bs///wp-content/uploads)
Warning: Currently configured WordPress plugins di

Thread Starter

MicF

(@micf)

9 years, 9 months ago

Here’s the debug output:

SitePush version: 0.4.2
SitePush options: OK
WordPress version: 3.9.1
WordPress multisite: No
Site: Berninger und Sananikone
PHP version: 5.2.17
PHP safe mode: off
Server user: u70095448
Server groups: uid=1199704(u70095448) gid=600(ftpusers) groups=600(ftpusers)
Server: Linux infong 2.4 #1 SMP Wed Apr 30 14:14:27 CEST 2014 i686 GNU/Linux
SitePush dir: /homepages/37/d428665981/htdocs/bs/wp-content/plugins/sitepush
WordPress abspath: /homepages/37/d428665981/htdocs/bs/
sites_conf: 0604 u70095448(1199704) ftpusers(600) (readable/parseable)
dbs_conf: 0604 u70095448(1199704) ftpusers(600) (readable/parseable)
wp-config: 0644 u70095448(1199704) ftpusers(600)
SitePush config for this site follows:

Array
(
    [cache] =>
    [caches] => Array
        (
            [0] => /caches/timthumb
            [1] => /caches/something_else
        )

    [label] => Live Site
    [wp_dir] => /
    [wp_content_dir] => /wp-con
    [domain] => bs-fdl.de
    [web_path] => /homepages/37/d428665981/htdocs/bs
    [db] => live
    [live] => 1
    [name] => live
    [default] =>
    [domains] => Array
        (
            [0] => bs-fdl.de
        )

    [admin_only] =>
    [wp_plugin_dir] => //wp-content/plugins
    [wpmu_plugin_dir] => //wp-content/mu-plugins
    [wp_uploads_dir] => //wp-content/uploads
    [wp_themes_dir] => //wp-content/themes
    [use_cache] => 1
)

I wonder where those double slash come from:

[wp_plugin_dir] => //wp-content/plugins
    [wpmu_plugin_dir] => //wp-content/mu-plugins
    [wp_uploads_dir] => //wp-content/uploads
    [wp_themes_dir] => //wp-content/themes

Actually I wonder where the wp-content comes from, because I tried to change this in the site config to something else (see above [wp_content_dir] => /wp-con), but still there in the debug.

Mic

Thread Starter

MicF

(@micf)

9 years, 9 months ago

After a lot of trial and error, I found out to omit the those vars in the config:

wp_dir
wp_content_dir

Now the folders are pushed, but the database not.

How can I push the database?
In the options everythings seems to be alright:
Path to mysql on this server. The current path appears to be OK.

Thread Starter

MicF

(@micf)