Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pushing Site from Local to Online Environment (and the reverse) Resets Base Location Setting #196

Closed
zoladesigners opened this issue Jun 3, 2021 · 7 comments · Fixed by #219
Labels

Comments

@zoladesigners
Copy link

This is in version 2.1.6 of the plugin

I am using the Child Theme Base Location setting, when I push the site to a live environment (ie on a domain name) or pull from a live environment to a local install this setting resets to Parent Theme.

@kvangorden21
Copy link

Same issue for me, @zoladesigners. Any fix?

@gcwebsites
Copy link
Collaborator

gcwebsites commented Sep 1, 2021

I have seen this from time to time too. So I am having the same issue.

And I am using the latest version of the plugin.

@kvangorden21
Copy link

Is this closed because it's been fixed or is it just identified as a bug?

@shadoath
Copy link
Collaborator

shadoath commented Sep 8, 2021

This is due to using an absolute path instead of a relative one for the CSS directories. I'll work on a PR to not store the aboslute path in the database instead loading it from the WP env.
@kvangorden21 its a known bug, no solution yet.

@shadoath
Copy link
Collaborator

shadoath commented Sep 8, 2021

From #207 as this provides a good explanation of the underling issue.

I am using an host providing me a staging environment. But in this case there are an issue. The path to the base location is stored as full path in wp_options table. But the path are different between live and staging:

Live: /home/wp/disk/wordpress/wp-content/...
Staging: /home/wp/disk/wordpress_staging/wp-content/...

So the generated css are not available. Is there a chance to change this, that only the part from wp-content/... will be stored in wp_options and the path to the wordpress installation is added during runtime? This would solve this issue.

@shadoath
Copy link
Collaborator

shadoath commented Sep 30, 2021

Has anyone been able to test #219?

@shadoath
Copy link
Collaborator

Last chance to test this before it is merged in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants