<bla bla bla> I am waiting for the day when Wordpress do all the above in order for it to be compatible with Google App Engine, and not the other way around. Would you change the car or would you change the road ? ( you are absolutely free to choose either, but not both ) </bla bla bla>
On Thu, Dec 12, 2013 at 10:29 AM, Vance Hallman <ventura...@gmail.com>wrote: > Lars and everyone else. Unless I am wrong this is the year 2013, almost > 2014. I think Microsoft, IBM, most forms of Linux, and Ubuntu all have auto > updates either as recommended or an option that is easily enabled. If you > want this to become a consumer platform (why else would you be doing this?) > you need to put a little faith in wordpress.org's PHP and javascript team. > > Not withstanding your pending updates to make it 3.7.1 compatible here are > a number of issues that you need to put on a roadmap for all of us to see. > And you need to do it quick. Why? Wordpress is on a "less than quarterly" > cycle for full blown major rev versions. 3.7 and 3,8 are HUGE steps in the > right direction as they are now documenting and organizing all of their > code along industry standard API releases. > > Here's the list and I invite comments, ideas, suggestions: > > 1. FTP and .htaccess easy access by not only app engine admins, but > wordpress logged in admins. > 2. You need to be updating your wordpress page with each minor rev. If > Microsoft, Amazon and IBM can do it Google can too. > 3. Rewrite your wordpress page as if you are a wordpress admin, NOT > someone who is a PHP, Python and MySQL expert. Show screen shots, show > examples, don't assum ANYTHING. > 4. As a start for number 3 the instructions call out for installing > various plugins at certain points. You only mention a few paragraphs later > to NOT activate them until post deploy. I've been a wordpress afficiando > since the early years of WP and I can tell you that 99% of all admins > automatically activate wordpress plugins upon install. It's INSTINCT and if > you want to change that behavior you need to tell them UPFRONT and in ALL > CAPS. > 5. You talk about Memcache Object Store and Batcache plugins but fail to > mention that their need to be installed locally if you want to troubleshoot > locally. > 6. Where are the tools for telling us whether or not when we deploy wether > or not those plugins are actually working when we activate them? I am 90% > sure I installed mine correctly but my appspot site is dog slow with > nothing installed but the 3 recommended plugins, which I have no idea if > they are working. > 7. Don't send us to StackOverFlow. Their are no easy ways to use > stackoverflow for this type of use case. Not to mention I have 3 > outstanding questions on SO that have lots of views and zero reply's. > 8. Give us an easy to use graphic that shows where the 87 cents I spent > today went so I know where to troubleshoot. I know no one is visting my > blank blog. So what is causing all of THIS? > https://cloud.google.com/console#/project/apps~fc1prod > 9. I have read in numerous places that I should be able to see my > Wordpress directory structure when I click on Google Cloud in the left hand > panel and my bucket in the right hand panel. All I see is blank page. > 10. I am still trying to wrap my arms around the purpose of Wordpress > using Google App Engine. It takes many, many hours to get anything done. > The entire configuration should be as fast if not faster than bitnami.orgor > S3. Those take a few minutes to spin up a complete WP site and enable > the WP admins to get to work and start building sites. > > Thoughts, ideas, comments? > > Thanks, > Van > > > > > > > > > On Friday, December 6, 2013 3:22:18 PM UTC-8, Mars Lan wrote: >> >> Thank you for bring this issue to our attention. The bug surfaces due to >> a change in WordPress 3.7 and affects only the development server. It >> should be fixed in the next release. Meanwhile, please manually change >> line 109 -110 of <google_appengine root>/google/appengine/tools/ >> devappserver2/php/runtime.py from >> >> user_environ['REAL_SCRIPT_FILENAME'] = environ[ >> http_runtime_constants.SCRIPT_HEADER] >> >> to >> >> user_environ['REAL_SCRIPT_FILENAME'] = os.path.normpath( >> os.path.join(self.config.application_root, environ[http_runtime_ >> constants.SCRIPT_HEADER])) >> >> As this is a Python script, make sure the new statement is indented >> correctly. >> >> >> On Saturday, November 30, 2013 7:47:58 AM UTC-8, OC2PS wrote: >>> >>> Looks like App Engine has trouble with WordPress 3.7.1 >>> http://wordpress.org/support/topic/trouble-running-local- >>> wordpress-in-google-app-engine >>> >>> This is terrible especially as WordPress have decided that they will >>> start automatically updating WordPress without human intervention! >>> >> -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
