On Thursday, December 5, 2013 9:00:44 PM UTC-5, Brian Quinlan wrote: > > On 5 December 2013 17:30, Gary Mort <gary...@gmail.com <javascript:>> > wrote: > > I was wondering if there are any best practice web sites on using PHP on > > Google App Engine. > > > > While working through installing the Joomla! CMS on GAE I've run into > some > > weird oddities and initially have taken a rather brute force approach to > > work through them. > > > > Being unhappy with the brute force method[which requires modifying core > > files in the open source code in order to accommodate GAE] I have > continued > > to cycle on it in the back burner and am trying an alternate approach > right > > now. > > > > Specifically, in Joomla there are 3 main entree points to an > application: > > http://mydomain.com/index.php > > http://mydomain.com/administrator/index.php > > http://mydomain.com/installation/index.php > > > > > > So far I've run into 2 issues: > > 1) Joomla uses XML files in order to define html form's. PHP is used to > > parse those files and then build the forms. GAE disables the ability to > > load /remote/ XML files in PHP by default. It is possible to allow this > by > > add libxml_disable_entity_loader to the list of enabled functions and > then > > to call libxml_disable_entity_loader(false); at some point in the code. > For > > some reason, despite the fact that these are LOCAL xml files Jooma > attempts > > to read, I still need to use this fix to allow Joomla to read the local > > files. > > > > 2) Joomla defaults to saving sessions in files, GAE defaults to saving > > sessions in memcache. Attempt to save session files using the default > > save_path does not work since the path does not exist. Making a small > hack > > to make memcache the default does not work because Joomla checks for the > > existence of the Memcache extension[via extension_loaded()] which does > not > > exist in GAE. > > I've filed a bug for this: > https://code.google.com/p/googleappengine/issues/detail?id=10371 >
Hmm, I assumed that what happened on dev would also happen up one gae..... Though personally I wasn't concerned with that one as a bug so much as the xml parsing - as there I need to be able to parse local files and the docs indicated it was only needed for processing remote files. I'm restarting my setup process in a new repo, https://github.com/garyamort/joomla-gae and things are going more smoothly this time. >From what I learned on the first pass, I'm providing some logical separation between basic GAE test code and where my website code will be going - and thanks to the ability to restrict specific url paths to only logged on administrators of my Google App Engine project - I'm able to deploy code debugging code to dump the php config and such without having to do any coding of my own to secure it - GAE does it for me. -- 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.
