Tag Info

New answers tagged

0

Ok, As it's front-end... I might: Set up the folder on the server so that WordPress can read/write (775 or 755 ordinarily works depending on how your server is configured in terms of user/group permissions). Allow a user on the front end to see the files or choose which file to delete Upon choosing the file, pass the parameter to an intermediary PHP ...


0

Not sure how you have set up your groups/owners on the WordPress folders but you could try adding the following line to your wp-config.php file: define(’FS_METHOD’,’direct’); This allows updates via the UI.


0

The best way is to define a new role. An easy way to accomplish this is with the role scoper plugin. Otherwise you'll just have to write that plugin yourself manually. Here is a basic example pulled from the Codex $result = add_role( 'basic_contributor', __( 'Basic Contributor' ), array( 'read' => true, // true allows this ...


0

There are actually 3 users that IIS access files with on .NET sites: IIS_IUSRS, IUSR, and NETWORK SERVICE Grant all 3 IIS users Read & Execute, List Folder Contents, Read permissions on the entire WP folder For file management (e.g. plugin/theme installation & updates), grant all 3 of the IIS users Full Control on the wp_content folder.


0

Try using absolute paths in src attribute. If your images are in your theme folder, you can use: <img src="<?php bloginfo('template_url'); ?>/yourImageFolder/yourImage.jpg" /> This way, URLs will be absolute even if you move your WordPress site to another server.


0

chgrp www-data .htaccess chmod a-wx .htaccess WordPress needs to write rules to .htaccess at some point, usually to do with how a URL is seen and re-written. www-data group may need write access.



Top 50 recent answers are included