Tag Info

Hot answers tagged

16

File manipulation and shell scripting is not often what you do with WordPress. At most something you do to it, like backup or deployment stuff. It is something WP itself and plugins try to keep to a minimum for good compatibility with different hosting environments. What kind of WordPress development is it actually going to be? Field is quite wide from very ...


13

If I were to hire a WordPress developer, my wish list would look like this: Knows HTML and CSS inside and out; Has at least a basic grasp of JavaScript; Knows their way around PHP, and produces beautiful code (clean, consistent, DRY) Has a good grasp of database design and SQL: if I show you a database schema and a few queries, can you tell whether they're ...


5

The code you posted is to have multiple wp-config.php-style wordpress configuration files with one codebase. the configuration is then based on the domain name. imagine the localserver is listening on http://localhost.localdomain/ (no idea which one is the default with ubuntu), then the configuration file would be: ...


3

Based on your needs, yes: you should probably be using a Network (WordPress with MultiSite enabled). All network sites run the same version of WordPress Each network site can activate its own Plugins. You can explicitly allow each site to manage its own Plugins. Each network site can have access to different Themes (though you will have to manage access to ...


2

Well, after lots of digging (before and after posting this question), I think I figured it out. As @s_ha_dum suggests, the reason behind the odd directory placement is likely a personal preference of the person who created the Ubuntu "wordpress" package. Perhaps it makes for easier partitioning of permissions, or it makes updates more safe (in case the ...


2

Unfortunately you can't use Vagrantpress and Composer directly together easily. Half of Vagrantpress is the WordPress setup itself which isn't compatible. If you still wanted to leverage the base work Vagrantpress has done with PHP, Apache, MySQL etc, you could fork it and modify their WP module found here: ...


2

By the looks of it loads the config file from the /etc/wordpress directory instead of from /usr/share/wordpress, where the package is installed by default, probably for security reasons. I would recommend not using the package and instead installing WordPress as you would with any other installation - the setup it uses here could affect you later on - the ...


1

My best educated guess is to perform a checklist on the following: Take a look at the virtual host configuration files for your domains, if you have access to them. Ensure that they agree with the corresponding WordPress installations on your machine(s). If your Virtual Host configurations are written correctly and as intended, then the next step is to ...


1

I created a symbolic link in the /var/www/ directory. ln -s /srv/www/wp-uploads/ wp-uploads and then (in settings-> media) set up the upload folder: wp-uploads and url path: http://<my-ip>/wp-uploads


1

Best Practice #1 One of the best practices is to let the PHP process to run under a different user (in your case: jdoe, jsmith, etc) than the web server user (in your case: httpd) and let only these users have the write permission. Of course, your web server may still need read permission for all these files. For this solution to work, you may need to go ...


1

I have solved this strange problem by myself. Share my experience to all. Find these 2 lines in /etc/php.ini upload_max_filesize 16M post_max_size 16M Add common before, so that change as: ;upload_max_filesize 16M ;post_max_size 16M And final, do not forget restart apache: service httpd restart via SSH. Then I could login into my site under linux ...


1

I think that setting all to 777 is not the most secure option. Basically, my favourite is to change the wordpress to the webserver's owner. Being: sudo chown -R www-data:www-data /var/www/ So that the webserver is responsible for handling changes. Also, you can change the rights to 755 for the whole /var/www branch sudo chmod -R -c 755 /var/www/ ...


1

Check the .htaccess file first, and the Settings > General area first to make sure it's not a level of security-by-obscurity that one of the initial users tried to implement. The easiest way is to change the name of the folder then see if your site breaks, since you can rename a folder a lot faster than moving directories, deleting then re-uploading, etc. ...



Only top voted, non community-wiki answers of a minimum length are eligible