by the way my webhost has safe mode on which cannot be changed. is this the problem and how can I work around it?

Hi there,

In actual fact WordPress seems often to check the *ownership* of the files, as well as the permissions. So you may need to somehow chown the themes folder.

If you have FTP access to the server, you could simply upload the themes from the ZIP file into place yourself (that's all the installation is doing, after all). Deactivate and reactivate and the nagging red error will go away.

Does that make any sense?

Let me know how you get on.

Thanks
James

I'm having the same problem on upgrade, so I did like you said and uploaded the files manually and set ALL permissions to 777, but I'm still getting this error:

Critical WordPress Mobile Pack Issue

Could not install theme files to /public_html/wp-content/themes/mobile_pack_green. Please ensure that the web server has write- and execute-access to that directory.

(Deactivate and re-activate the WordPress Mobile Pack once resolved.)

Hmm - this is strange, since the code in the plugin does nothing more than check that the folder is writeable (and executable so it can be listed to check the files are inside)

Bear in mind that this message appears continually until the pack is deactivated and reactivated (which is when it does the check)

If you are sure that the v1.1.1 themes are all there and in the right place, you could also simply disable the check. Comment out lines 133 and 134 in wordpress-mobile-pack.php

Commenting is done in PHP by prepending lines with //

I know this is not satisfactory, but I've not been able to reproduce, and this is a last resort to get you going for now.

What are the permissions on the mobile_pack_green folder itself? Are they different to the themes parent?

Thanks
James

Greetings James:

What I'm finding with v1.1.1 of your plug-in is:

On a new "clean' installation of WP 2.8.2 it up upgrades or installs perfectly.

However, on "older" installations (2.8.0 upgraded to 2.8.1, etc) the error messages "Not be able to cache images", "Not able to install theme files" and "please ensure that the web server has write- and execute-access to that directory." Happens like clock work.

Hope this helps.

Cheers.

Allan

Hi guys,

I appreciate that the permissions thing is a real pain... and I can see that safe-mode doesn't help either.

I also realise that changing ownership is difficult unless you have shell access.

The plugin is over-cautious at install time because we were having trouble with people who thought things were OK, but in actual fact they weren't (and then WordPress failed spectacularly).

If you have 777 on those folders (and all the ones beneath), in actual fact, things may all be well. Perhaps I need to relax the error reporting for those cases where it's not perfect but things may still work.

James

FYI - this is still a problem in the new 1.1.2 version

Running a new WP installation on our own Apache under windows.

I have the same Problem. WP 2.8.4 on a Windows Apache Server

it's an conflict with the ownership rights on windows.
linux and windows is different in ownership.

i uncomment line 111 to 121 in the "wordpress-mobile-pack.php" then it works.

but one update -> overwrite this file -> crash

have u an solution for this problem?

PS: My other blog running under linux -> the plugin works great

thanks
mbaiti

Are there any updates on this issue. I made a clean install and have the same problem.
Changes permissions for the mentioned directories to 777 even, and still problem persists.

Just updated to 1.1.3 and it's still a problem on Windows.

Can a 'Ticket' on http://www.assembla.com/spaces/wordpress-mobile-pack/tickets be created for this error?

Hello Wordpress Fans,

I got this problem also, and solved it. php-functions like is_writable() seem to behave a little diferent in safe mode. See my post check-writeable-dirs-install-fails-path-delimiter-needs-added
(I still needed to copy the theme files manually. the software created subdirs, but was not able to copy files into them. It not really clear to me why now.)

Hope this helps

Karsten Meier
--
Handylearn Projects creates mobile software.
www.handylearn-projects.de

hey everybody!

i am running the current wordpress 2.8.6 and just as the posters above have the same problems installing the mobi pack, same issues with permission, also with setting any file to 777.

meier above me posted a fix as it seems but since i am no php-surgeon i feel not cunning enough to incorporate the changes on the right spots, so i was hoping the release got the fix in the meantime?

since i run my blog in a subfolder on the server ("/blog") i am guessing that this can be a part of the problem?

help is much appreciated! (i hope somebody still reads this old thread though....)
phil

Hi guys,

This seems like it could be a fantastic plugin, but I'm having the same problem.

I'm running WP 2.9.1 and WPMP 1.2.0, all the relevant folders are set to 777 and the ownership is correct, running on a Unix host.

I've managed to fix the cache is_writable error using Karsten Meier's fix (check-writeable-dirs-install-fails-path-delimiter-needs-added), but the /themes folder still generates the following error and I'm stumped:

That portion of my readiness audit code in wordpress-mobile-pack.php reads as follows:

  $theme_dir = str_replace('/', DIRECTORY_SEPARATOR, get_theme_root());
  $theme_does = '';
  if (!file_exists($theme_dir)) {
  	$theme_does = __("That directory does not exist.", 'wpmp');
  } elseif (!is_writable($theme_dir)) {
  	$theme_does = __("That directory is not writable.", 'wpmp');
  } elseif (!is_executable($theme_dir) && DIRECTORY_SEPARATOR=='/') {
  	$theme_does = __("That directory is not executable.", 'wpmp');
  }
  if($theme_does!='') {
    $ready = false;
    $why_not[] = sprintf(__('<strong>Not able to install theme files</strong> to %s.', 'wpmp'), $theme_dir) . ' ' . $theme_does . ' ' . __('Please ensure that the web server has write- and execute-access to it.', 'wpmp');
  }

Thoughts?

Hi

Same problem - tried alsorts, currently in wP 2.8.4. From reading this thread it seems to be a common enough issue.

Are there any updates?

Thanks

Stu