Can't upgrade past 3.6.2 (Windows, PHP 5.6) - Joomla! Forum - community, help and support
we've been having problems upgrading past joomla! 3.6.2 on windows server running php 5.6
each time white screen (frontend , admin panel). use manual unzip+upload file upgrade method, , have never had problems in past doing way.
after few months of trying , re-trying - watching 3.6.3, 3.6.4 , 3.6.5 come along - got upgrade work... database edits , small hack 1 file. post offer insight joomla! devs , other users.
at first, json-related thread looked promising in helping fix problem viewtopic.php?p=3436438#p3436438. and, in turn, script https://robertwent.com/blog/joomla/102- ... omla-3-6-3. using both, removed dodgy null/empty entries in our database... still white screen persisted upgraded 3.6.4 or 3.6.5.
attacking other side, tried fresh install using full 3.6.4 pack. failed instantly @ first installation screen. led conclusion problem wasn't (necessarily) database @ all, , must linked either our php version, or windows environment. it's worth noting similar joomla! upgrades 3.6.4 on apache have worked fine.
another forum thread mentioned copying '/libraries/' folder 3.6.2 pack failed 3.6.4 site... did, , failed installation went through successfully, surmised there file in 3.6.4 pack causing incompatibility.
to cut long story short, problem file (for us) '/libraries/vendor/composer/autoload_real.php'.
in 3.6.4 , 3.6.5, there php version check conditionally loads in 'autoload_static.php' file. had disable condition in '/libraries/vendor/composer/autoload_real.php' (in effect, putting 3.6.2 version *doesn't* contain same condition) commenting out line (line 26);
we commented out line in 3.6.4 site work, , morning upgraded 3.6.5 - site died white screen (again) commented out line above, came life.
we believe json-related fixes rid invalid null/empty database entries part of fix in established site, please go through process if you're having problems upgrade opposed fresh install.
i don't know windows , php 5.6, hope post helps somebody.
each time white screen (frontend , admin panel). use manual unzip+upload file upgrade method, , have never had problems in past doing way.
after few months of trying , re-trying - watching 3.6.3, 3.6.4 , 3.6.5 come along - got upgrade work... database edits , small hack 1 file. post offer insight joomla! devs , other users.
at first, json-related thread looked promising in helping fix problem viewtopic.php?p=3436438#p3436438. and, in turn, script https://robertwent.com/blog/joomla/102- ... omla-3-6-3. using both, removed dodgy null/empty entries in our database... still white screen persisted upgraded 3.6.4 or 3.6.5.
attacking other side, tried fresh install using full 3.6.4 pack. failed instantly @ first installation screen. led conclusion problem wasn't (necessarily) database @ all, , must linked either our php version, or windows environment. it's worth noting similar joomla! upgrades 3.6.4 on apache have worked fine.
another forum thread mentioned copying '/libraries/' folder 3.6.2 pack failed 3.6.4 site... did, , failed installation went through successfully, surmised there file in 3.6.4 pack causing incompatibility.
to cut long story short, problem file (for us) '/libraries/vendor/composer/autoload_real.php'.
in 3.6.4 , 3.6.5, there php version check conditionally loads in 'autoload_static.php' file. had disable condition in '/libraries/vendor/composer/autoload_real.php' (in effect, putting 3.6.2 version *doesn't* contain same condition) commenting out line (line 26);
code: select all
// $usestaticloader = php_version_id >= 50600 && !defined('hhvm_version');
we commented out line in 3.6.4 site work, , morning upgraded 3.6.5 - site died white screen (again) commented out line above, came life.
we believe json-related fixes rid invalid null/empty database entries part of fix in established site, please go through process if you're having problems upgrade opposed fresh install.
i don't know windows , php 5.6, hope post helps somebody.
no wonder experiencing issues, reported many times shouldn't update way. proper way update use joomla! update component. manual way works postupdate.php mbabker.beverleyh wrote:we've been having problems upgrading past joomla! 3.6.2 on windows server running php 5.6
each time white screen (frontend , admin panel). use manual unzip+upload file upgrade method, , have never had problems in past doing way.
any other way doesn't update properly, there no proper description detailed enough describes actions do. instructions on docs.joomla.org wrong!
consider 1 of bad changes cause interruptions on existing sites. similar changing of phpmailer. bugfix such may correct, implementation sucks. expect better impact analysis , phased approach. data corruption should have been logged allow correction without disruption.beverleyh wrote:at first, json-related thread looked promising in helping fix problem viewtopic.php?p=3436438#p3436438. and, in turn, script https://robertwent.com/blog/joomla/102- ... omla-3-6-3. using both, removed dodgy null/empty entries in our database... still white screen persisted upgraded 3.6.4 or 3.6.5.
the current behaviour allowed major releases, not acceptable minor or patch releases! in addition expect proper use of relational database, accepting null value of database, not programming in code! welcome 21st century!
beverleyh wrote:to cut long story short, problem file (for us) '/libraries/vendor/composer/autoload_real.php'.
in 3.6.4 , 3.6.5, there php version check conditionally loads in 'autoload_static.php' file. had disable condition in '/libraries/vendor/composer/autoload_real.php' (in effect, putting 3.6.2 version *doesn't* contain same condition) commenting out line (line 26);code: select all
// $usestaticloader = php_version_id >= 50600 && !defined('hhvm_version');
thanks reporting here, did report issue joomla?
Comments
Post a Comment