- #Cth 470 a supported tablet was not found update#
- #Cth 470 a supported tablet was not found upgrade#
- #Cth 470 a supported tablet was not found full#
- #Cth 470 a supported tablet was not found code#
Regards, and hope you readily find the clarity on this,ĭid you make sure to update your MSM files as well? MSM 2.1.2 is required for ExpressionEngine 2.4. It is true that this site has deliberately been upgraded steadiily from some quite pre 1.6 days, just to catch issues such as this may be. _Why_ it’s sometimes needed, but you don’t put it by default in route.php. I think the strong clue is the missingness of this particular route.php line, which you apparently knew something about a long time ago. I still have some suspicion that the underlying issue is actually configuration held in the database, quite possibly in one of those #$%#& php-array-encoded fields. Just so you know, I did a lot more than reported here, in trying to assure that my pre-upgrade-attempt config was very sanitary, both in php files and in the database.
However, there must definitely be something, as it’s a hard fail. I did diffs on many related config and EE source files, and couldn’t note anything related that changed since 2.2.1, as my hosted system was before upgrade. I figure you guys and devs will want to clearly trace this down.
#Cth 470 a supported tablet was not found upgrade#
What I don’t understand is how it can work any other way? Why did my laptop mirror upgrade fine? What’s different compared to all the successful upgrader’s systems? The whole way the installer is magically patched in when present seems to depend on the fix’s added route being there. This edit of the Routes.php file in the installer is logical, given what I found in the router itself. Note that Lisa believes the need is due to ‘some hosts’, though I am on EE’s own EngineHosting where the problem arose. Here’s a link back to what seems the original of this alteration, which gives instructions: Routing Fix. It’s just altering what amounts to a configuration file, not actual EE code, and in the installer only. Oxford, you can try it, and see if it solves for you. Ok, I have a fix that let me upgrade successfully to 2.4.0, with site back up and fully functional after also doing a required Solspace Tag update. This is wrong, and has I suspect may have to do with the way the installer has to have a short path added in routes.php.
#Cth 470 a supported tablet was not found full#
No MSM involved here, and I note that the original poster’s site is a 2.2.2 -> 2.4 upgrade.Īdditional Edit 2 March 2012: clarified that it was a full server path required to get the logging to work - with default there was no log folder created, and no logs present. Is there some need to do a 2.3.1 upgrade before 2.4? Not easily possible at this time, and shouldn’t be required. The live site, however is actually 2.2.1. This site has been upgraded many times, without problems like this.Įdit: Actually, the site mirror on the laptop was upgraded from 2.3.1-without problems. Others have had this problem in recent days, also, if you look at support postings. I may suspect this is a further clue that something basic is going wrong in routing. I had to also configure a hard-coded full server path to a directory-then it would work. However, it’s not at all clear why Codeigniter is trying to validate the admin.php file, since it’s already been used, and the wizard is primed to start via routes.php.įurther, I couldn’t get codeigniter system logging to work by default setting of level to 4.
#Cth 470 a supported tablet was not found code#
The APPPATH is what it should be, due to the code in admin.php when the installer is in place, and if I test by renaming the installer, I instead get the CP login as expected. APPPATH is pointing to /hostpath/./system/installer/ This shows that the failure is at the end of _validate_request: the bailout on line 286.
I had no trouble updating a mirror of this site on a laptop-but on EngineHosting, I get that same ‘The page you requested was not found.’ message.Īfter trying a fresh download, much scrutinizing of config files, etc., I took a practical step and enabled system logging as well as placing some debug code in codeigniter/Router.php, as this was where the fali occurred. Dan, I’m having the same problem, updating a site from 2.3.1 to 2.4.0.
0 kommentar(er)
