python appcfg.py update <wordpress app location> does not reflect the change on server

[dwipin chandran]

Hi,

I have a local setup of wordpress.org along with a local MySQL. I completed the changes on my local that includes changing the theme and adding new posts.

When I run the "python appcfg.py update <wordpress app location>", I get no errors. Here's the output -
ubuntu@ubuntu-VirtualBox:~/google_appengine$ python appcfg.py update /home/ubuntu/shiniskitchen/
01:41 PM Application: shiniskitchen; version: wpfromstarterproject
01:41 PM Host: appengine.google.com
01:41 PM
Starting update of app: shiniskitchen, version: wpfromstarterproject
01:41 PM Getting current resource limits.
01:41 PM Scanning files on local disk.
01:41 PM Scanned 500 files.
01:41 PM Scanned 1000 files.
01:41 PM Cloning 699 static files.
01:41 PM Cloning 1161 application files.
01:41 PM Compilation starting.
01:41 PM Compilation completed.
01:41 PM Starting deployment.
01:41 PM Checking if deployment succeeded.
01:41 PM Deployment successful.
01:41 PM Checking if updated app version is serving.
01:41 PM Completed update of app: shiniskitchen, version: wpfromstarterproject
01:41 PM Uploading cron entries.

However when I try to access the public URL, I got a blank screen. The blank screen was because I had changed the theme and deleted the rest of the themes including the default one.
This is my second deployment of this app, my first deployment was with a different theme and I was able to see the changes immediately.
Please let me know if I am missing something.

Thanks,
Dwipin Chandran.

[Patrice (Cloud Platform Support)]

Hi Dwipin,

When yo say "the public URL", do you mean "shiniskitchen.appspot.com"? Because you seem like you deployed this on a new version, "wpfromstarterproject". Since this version is not your default, when you go to "shiniskitchen.appspot.com", you won't go to that version. You would need to hit "http://wpfromstarterproject.shiniskitchen.appspot.com/"

If I try both URLs, I get two very different views, but the one targeting your version actually returns in an error.

Let me know if that helps

Cheers!