but if i change with other template is working, is limitation for size of template ?
Revo 2.2.4 pl mobileDetection 2.1.0 pl . PHP 5.3.14 Hosted on Lunarpages
I've been happily using the mobileDetection plugin but recently the error log is clogging up with debug errors - Mb's per day. This may have happened since the last revo update without me spotting it. I don't think that it is installation specific as it occurs on at least one other web site.
extract from the log:-
[2012-09-18 23:27:38] (DEBUG @ /index.php) An error occurred while trying to cache lexicon/en/core/all_other_mobile (lexicon/language/namespace/topic)
[2012-09-18 23:27:38] (DEBUG @ /index.php) An error occurred while trying to cache lexicon/en/core/all_other_mobile (lexicon/language/namespace/topic)
[2012-09-18 23:27:38] (DEBUG @ /index.php) Language string not found: "Should basic cellphones be treated as a mobile device?"
[2012-09-18 23:27:38] (DEBUG @ /index.php) Language string not found: ""
[2012-09-18 23:27:38] (DEBUG @ /index.php) An error occurred while trying to cache lexicon/en/core/usecookie (lexicon/language/namespace/topic)
[2012-09-18 23:27:38] (DEBUG @ /index.php) An error occurred while trying to cache lexicon/en/core/usecookie (lexicon/language/namespace/topic)
[2012-09-18 23:27:38] (DEBUG @ /index.php) Language string not found: "Should detection be stored in a cookie and only run the first time you visit a webpage?"
[2012-09-18 23:27:38] (DEBUG @ /index.php) Language string not found: ""
I'd appreciate any advice on how to handle this and thanks for a great plugin
Thankyou for the mobiledetection-plugin!
There is a very small issue, that produces debug-notifies in MODX-debug-mode: before the Cookie is set, the index 'browser' is not set. You can avoid this message e.g. this way. It is only a debug-notify and not an error, but I like clean debug-logs ;-)
... (line 194)
//Instantiate the object to do our testing with.
$uagent_obj = new uagent_info();
$var = ''; // add this
if (!empty($_GET[$force_browser_variable])) $var = $_GET[$force_browser_variable]; // and this
if($var == $force_browser_mobile){
...
Quote from: erhard at Sep 28, 2012, 01:32 PMThere is a very small issue, that produces debug-notifies...
Thanks for that fix. I'm a new ModX user and just ran across this too. The debug notification seems to trigger another error
reported here.
Loved ModX when I was using it a few years ago. Shifted to WordPress, sorry. Thanks, all.
Does MobileDetection 2.1.0pl extra need resources to be not cachable?
I'm running a Modx Revo 2.2.8pl site with MobileDection to change the contents of my templates using the <mobile> and <standard> tags.
I've never had any problems with it serving up mobile or standard pages and I always made the assumption that the resources need to be uncached and that how I was setting them.
The site regularly hosts new articles (created by other users) and I've just relised that many of them have the 'Cacheable' option checked. Again, they seem to work fine rendering with <mobile> or <standard> versions.
I thought if they were cached then it would only serve the version of the resource the first time it was cached. Am I missing something? Does it matter if they're set to cacheable?
Many thanks
Hi! Unfortunately Mobile Detection isn't working in the latest ModX 2.3 or am i doing something wrong? Any suggestions on what could be done about this?
Thanks for letting me know!
Hi Randomio!
Nice to hear that! I checked the logs but unfortunately there is nothing to see there. At least i couldn't figure out if something here belongs to mobile detection.
The symptoms are, that when i visit the site with a mobile device the page is blank. There is nothing to see at all.
In my "normal" page the site looks normal so the tags still work. Everything that is under <mobile></mobile> is not shown.
Hope this helps?
Any news on this? The Mobild Detection still is not working in the recent modx.
