Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • I’ve noticed that updating the plugin or toggling caching off and on tends to reset multiple settings including caching mode, mobile support and garbage collection scheduling to their defaults.

    plugins/wordpress-mobile-pack/themes/mobile_pack_base/groups/nokia_mid/images/kaltura.php is not a file that’s included in the WPMP download zip.

    Your site likely got hacked and that file was inserted by the hacker.

    Thread Starter yeswap

    (@yeswap)

    Thanks Joesph,

    Theres nothing in my server error logs and there have been no connectivity issues reported for either site. Pingdom is checking connectivity to the sites every 60 seconds 24/7 and shows no problems either.

    The fact that two sites on different servers experienced this issue shortly after the upgrade to 2.5.3 points to either a problem with the update or a connectivity issue on Akismet’s end. As the error hasn’t recurred I suspect the latter.

    Also, the fact that the error wasn’t cleared after I successfully connected to the Akismet servers by pressing the “Check for spam” button seems to be a bug.

    It sounds like you copied functions.php into your custom theme.

    Don’t copy all of the files in the base theme into the custom theme. Only copy the ones you want to modify.

    And unless you are fairly proficient in PHP don’t modify or copy functions.php as it requires special handling.

    Set the subdomain to point to the same folder as your main domain. There is no need to modify .htaccess, the pluging will detect mobile user agents and redirect them to mobile versions of the pages.

    If you want WPMP to work just like WP_Touch set Switcher Mode to “Browser Detection” That will work out of the box with no need for a subdomin.

    I’m getting the same message:

    Warning! /home/boostapp/public_html/ is writable. Please make it readonly after your page is generated as this is a security risk.

    chmod’ing /home/boostapp/public_html/ to 755 did NOT make the message go away and neither did chmod 711

    What permission attribute is WP Super Cache looking for? Everything I’ve ever read on security recommends 755 or 711 for web root directories.

    Thread Starter yeswap

    (@yeswap)

    Any progress on this issue? My boostapps.com site is targeted at users with low-spec mobiles using the Openwave 7 browser. Any page with more than 10 or so comments is failing to load in Openwave with a “Page too large for available memory” error. I’m running WPMP 1.2.0

    Thanks, sam.psb. Your fix works for me.

    Until I upgraded to 2.7, I did a lot of the administration of my blog on my mobile phone using Opera Mini. Mostly approving and editing comments, writing and editing posts. With 2.7 the administrative functions are largely unusable with Opera Mini.

    Issues:

    1. It’s impossible to edit comments in the moderation queue. The “Edit” link is hidden until you roll the mouse over it. In Opera Mini it’s just hidden with no way to invoke it. The same is true of the “Approve”, “Delete” and “Spam” links but I can still get to these functions by tagging comments and using the “Bulk Actions” drop down. Could edit perhaps be added to bulk options to resolve this?

    2. Saving new and edited posts does not work. I can edit posts and and create new ones but when I click “Save Draft”, “Publish” or “Update Post” although it appears to work (when the screen refreshes. ‘Post Updated’ appears), nothing is actually saved. In addition, after a failed save, the “Save Draft”, “Publish” or “Update Post” buttons are disabled so it’s not even possible to retry.

    I tried the mobileAdmin and WPadmin plugins and neither work with 2.7. At this point I see no alternative but reverting to 2.6.5 as I can’t live without the ability to edit comments and create and edit posts from my phone.

    So I’m pleading with the WordPress.org development tema, please test administrative functions in Opera Mini and if at all possible provide a way to perform basic admiistraive function using it and other “Full-web” mobile browsers.

Viewing 9 replies - 1 through 9 (of 9 total)