Wont' load with Upgrade

@worthywp would you mind letting me know:

– What’s the WordPress version your using? Notice, it should be 3.5+

– What was the previous version of WordPress Mobile Pack ? Was is 1.2.5 or 2.0?

– What was the browser you used on iPhone?

– What’s the URL of your blog, I’d like to have a look and see if I can figure it out. Also, if you could enable the plugin just for a bit to debug this on our end, that would be really helpful.

Later edit: just noticed that you’ve posted related issues on other threads and @florentina.opris answered some of them. I’ll let her help you ??

@worthywp,

In order to debug your mobile app you can go to themes/index.php and replace “app.js” with “app.extended.js”. Then open the app in Safari with the iPhone User Agent set and an open console(right click -> inspect element -> Console tab) and check if there are any errors returned by the app.

Then access this link: https://www.worthynews.com/wp-content/plugins/wordpress-mobile-pack/export/content.php?content=exportcategories&limit=2&descriptionLength=50 and check if it returns a JSON.

If there are no errors in the console and there is a JSON returned by that url, the application should work, so you can check if there are any errors in the admin area by opening wp-config.php and setting WP_DEBUG to true.

Please let us know what the errors are so we can help solve the issue.

Ok I replaced the app.extended.js and opened Safari with iPhone User Agent set.

The error that comes back —

Get the url of my site /plugins/wordpress-mobile-pack/export/content.php?content=exportcategories& dc=1402584055610&limit=9&descriptionLength=300&page=1&start=0&callback=Ext.data.JsonP.callback1 500 (Internal Server Error)

TypeError: ‘undefined’ is not an object (evaluating ‘firstCategory.get’)

Thanks,

Worthy

– What’s the WordPress version your using? Notice, it should be 3.5+ — The latest — 3.9.1

– What was the previous version of WordPress Mobile Pack ? Was is 1.2.5 or 2.0? 2.0.1 — 2.0 was working fine, except ONE category couldn’t load.

– What was the browser you used on iPhone?
Safari

@worthywp,

There may be an error in the export that send the information to the app.

The errors there are disabled in order for the app not to crash when there are small notices, so could you please:

1. Go to plugins/wordpress-mobile-pack/export/content.php
2. Remove the line “error_reporting(0);”
3. Open in any browser https://www.worthynews.com/wp-content/plugins/wordpress-mobile-pack/export/content.php?content=exportcategories& dc=1402584055610&limit=9&descriptionLength=300&page=1&start=0&callback=Ext.data.JsonP.callback1

And let me know if there are any error?
Also, could you tell me what’s the WordPress version you’re using?

If you do not manage to change that file, please contact me at florentina[at]appticles[dot]com and I will send you the updated file for testing.

I removed the line error_reporting(0);

I went to the URL and didn’t see a issue.

I removed the space between & dc etc

As I went to the site again,

I’m getting the same error, and the Type error is in app.extended.js:73418 if that means anything.

I’m using latest WordPress – 3.9.1

Thanks

@worthywp

Can you please check if the content categories are enabled in the ‘Content’ section (WMP admin area)? At least one of them has to be ‘active’.

If they are active, there might be an error on that page (content.php) that’s causing the content not to load properly. In this case, is it possible for you to enable debug mode (WP_DEBUG set to ‘true’ in the wp-config.php file)? It doesn’t have to stay like that, just for a few seconds so we can figure out the error. If you have an error_log file, that’s even better.

Btw, there aren’t many differences between 2.0 and 2.0.1, only a few lines of the code in the export files, that’s why we are still trying to figure it out.

I found this in the wordpress-mobile-pack/export/ folder. A snippet of the error log. Does this help?

[12-Jun-2014 16:09:00] PHP Fatal error:  Uncaught exception 'LogicException' with message 'Passed array does not specify a callable method' removed-path-for-security/plugins/wordpress-mobile-pack/libs/htmlpurifier-4.6.0/library/HTMLPurifier/Bootstrap.php:117
Stack trace:
#0 removed-path-for-security/plugins/wordpress-mobile-pack/libs/htmlpurifier-4.6.0/library/HTMLPurifier/Bootstrap.php(117): spl_autoload_register()
#1 removed-path-for-security/plugins/wordpress-mobile-pack/libs/htmlpurifier-4.6.0/library/HTMLPurifier.autoload.php(11): HTMLPurifier_Bootstrap::registerAutoload(Array)
#2 removed-path-for-security/plugins/wordpress-mobile-pack/libs/htmlpurifier-4.6.0/library/HTMLPurifier.auto.php(9): require_once('removed-path-for-security/pub...')
#3 removed-path-for-security/plugins/wordpress-mobile-pack/export/export-class.php(4): require_once('removed-path-for-security/pub...')
#4 removed-path-for-security/plugins/wordpress-mobile-pack/export/content.php(5): require_once('removed-path-for-security/pub...')
#5 {main}
  thrown in removed-path-for-security/plugins/wordpress-mobile-pack/libs/htmlpurifier-4.6.0/library/HTMLPurifier/Bootstrap.php on line 117
[12-Jun-2014 16:09:29] PHP Fatal error:  Uncaught exception 'LogicException' with message 'Passed array does not specify a callable method' in removed-path-for-security/plugins/wordpress-mobile-pack/libs/htmlpurifier-4.6.0/library/HTMLPurifier/Bootstrap.php:117
Stack trace:
#0 removed-path-for-security/plugins/wordpress-mobile-pack/libs/htmlpurifier-4.6.0/library/HTMLPurifier/Bootstrap.php(117): spl_autoload_register()
#1 removed-path-for-security/plugins/wordpress-mobile-pack/libs/htmlpurifier-4.6.0/library/HTMLPurifier.autoload.php(11): HTMLPurifier_Bootstrap::registerAutoload(Array)
#2 removed-path-for-security/plugins/wordpress-mobile-pack/libs/htmlpurifier-4.6.0/library/HTMLPurifier.auto.php(9): require_once('removed-path-for-security/pub...')
#3 removed-path-for-security/plugins/wordpress-mobile-pack/export/export-class.php(4): require_once('removed-path-for-security/pub...')
#4 removed-path-for-securityplugins/wordpress-mobile-pack/export/content.php(5): require_once('removed-path-for-security/pub...')
#5 {main}
  thrown in removed-path-for-security/plugins/wordpress-mobile-pack/libs/htmlpurifier-4.6.0/library/HTMLPurifier/Bootstrap.php on line 117

[Moderator Note: Please post log files between backticks or use the code button.]

I initially had ALL the categories checked (which is like 100), however I removed them all to a single category that doesn’t have any spaces / extra characters like – or . and the same error is shown.

If you go to https://www.worthynews.com on mobile, I’ve left the mobile pack on so you can debug.

Thanks, this error is what we were looking for. I’ll take a look and get back to you asap.

We found a problem in the HTMLPurifier library that is used to parse the articles content before exporting them for the app. This library is the same in v2.0 and v2.0.1, but there seems to be a problem with the way it autoloads files (maybe a conflict with WP or another plugin).

I wasn’t able to find the right combination to reproduce the error on our end, so please let me know if the below change helps.

In the plugin, export/export-class.php, just at the beginning of the file, replace the line:

require_once '../libs/htmlpurifier-4.6.0/library/HTMLPurifier.auto.php';

with

require_once '../libs/htmlpurifier-4.6.0/library/HTMLPurifier.safe-includes.php';

That solved the issue. Even the category that had an issue before loads without a hitch.

Plugin check if you want to look and try to replicate the issue.
Akismet
All in One SEO Pack
Google News XML Sitemap
HyperCache
iThemes Security
Jetpack
Jetpack Post Views
List Category Posts
MetaSlider
NextScripts: Social Networks Auto-Poster
Sharebar
Use Google Libraries
WordPress Mobile Pack
WP-PageNavi
WP Retina 2x

When I first got the error, I assumed it was iThemes Security, however that wasn’t the issue.

Then I disabled HyperCache, thinking that was the issue, however that also didn’t fix the error.

The only one that I think could be directly related is Retina 2x if the mobile theme pulled retina images automatically.

Other than that, everything else shouldn’t affect the mobile theme.

Glad to hear it works now ??

Thank you for the plugin check, I will install those plugins on 3.9.1 and see if there are any compatibility issues.

Thanks a lot for the help in getting to the bottom of this!