I have requirement of Drupal project which is a commerce website. We have used Drupal commerce module for the same purpose before.
I have Centos 7 as my server with EasyApache installed. Everything is installed on the server to run Drupal project and normal Drupal project is working nice.
I have tried to make multisite working for my website. Tried many options:
Added subsite under sites folder (example.com)
Added site link in sites.php file ($sites['example.co'] = 'example.co';)
Created virtual host and symlink
And many more..
There are too many finding for multisite on Google but none of them is working well for me.
Can someone help me to configure multisite on centos 7 server?
You can set your domain.com/web/sites/default/settings.php add your host like this :
$settings['trusted_host_patterns'] = array(
'^example\.co$',
'^www.example\.co$',
);
On linux if you can't due of rights to set it, just change the rights of folder parent and the file.
sudo chmod 777 default
sudo chmod 777 settings.php
After the fix you can reverse to rights by :
sudo chmod 555 default
sudo chmod 444 settings.php
On the admin site you need to set it too and at first time if didn't do it.
Related
After update to Catalina i setup apache and mysql on localhost. I have files in /Users/myname/Sites folder. Wordpress website is running well, but i cannot upload media or install plugins, as website doesn't have permissions to folders/files.
I've tried to set CHMOD to folders, so user _www has the right permission, but still cannot create files and folders.
I also tried to change user for apache, but then website didn't work at all.
How can i add the right permission to _www user to write files?
Solved
It helped at the end to add _www user to _www group (if i understand fine)
sudo chown -R _www:_www /Users/myname/Sites/
I am using a Wordpress Multi-site instance on AWS Lightsail and have a couple different Wordpress sites hosted with no issues (in the same instance).
I would like to host another website to the same Bitnami instance, but this domain does NOT have a Wordpress site. It is just a standard PHP website.
I assume that I need to point the nameservers to the AWS servers, but I am not sure how to specify what directory to point the non-Wordpress domain to.
For my Wordpress domains, I was able to use the "Sites" feature in Wordpress to configure multiple Wordpress domains.
Since this new domain isn't going to be a Wordpress site, do I need to modify the httpd-vhosts.conf file or something else? What specifically do I need to add?
Bitnami Engineer here. You can copy the WordPress configuration files to a new folder
sudo mkdir -p /opt/bitnami/apps/myapp/{conf,htdocs}
sudo chown -R bitnami:daemon /opt/bitnami/apps/myapp/htdocs
sudo cp -r /opt/bitnami/apps/wordpress/conf/*.conf /opt/bitnami/apps/myapp/conf/
and then perform the following changes
Edit the configuration files inside the /opt/bitnami/apps/myapp/conf/ directory. The httpd-prefix.conf should configure the Alias directive and you need to remove the DocumentRoot (remember to change the paths to the new ones). The httpd-app.conf should configure the Directory where your application is (remember to change the paths to the new ones)
Include the new httpd-prefix.conf file in the /opt/bitnami/apache2/conf/bitnami/bitnami-apps-prefix.conf file
Restart Apache
sudo /opt/bitnami/ctlscript.sh restart apache
You can obtain more information in our documentation guide
https://docs.bitnami.com/aws/apps/wordpress/administration/create-custom-application-php/
Everything was going so well: installed XAMPP on Mac (OS 10.10.2). Installed Bitnami WordPress module. Imported existing WordPress site (this site is already live). Then imported/installed the theme I want to modify. All good up to that point.
Now I want to create a child theme. Following the instructions from Themify, which are great. BUT: I can't open the htdocs directory within the wordpress dir that was installed by the Bitnami module. No permissions.
There's a help page, but it's not helping me. Reason 1: I open FileZilla, I FTP to localhost, but the wordpress dir is nowhere to be found there. Reason 2: I try to follow their sudo chown instructions but the path is not valid for me. I tried:
$ sudo chown daemon:daemon Applications/XAMPP/xamppfiles/apps/wordpress/htdocs
... but no luck. "No such file or directory." I can find this folder in the Finder (see screencap), but I can't seem to access it from the command line. (Is that because XAMPP is in the Applications directory?)
In case it's not obvious, I am doing all this to muck around with my child theme offline. But I can't get my child theme folder into the wp-content/themes folder, because I can't FTP or access the folder directly through the Finder.
I was able to change permissions through the Mac "Get Info" panel. Doh!!
"Get Info" panel, unlocked
See screencap.
Try and put a Leading slash at the front of the directory listing so run this instead:
sudo chown daemon:daemon /Applications/XAMPP/xamppfiles/apps/wordpress/htdocs
Just go to /Applications/XAMPP/xamppfiles/htdocs/mysite/wp-content/themes/your-child theme and set permission of your child theme folder to writable to everyone.
I'm attempting to create Drupal Multisite. Currently lets say we have below Live Sites in the form
abc.example.com
def.example.com
xyz.example.com
All the Sites are present on the Same server (Nginx Server) in the directories
/var/www/vhosts/abc.example.com/httpdocs
/var/www/vhosts/def.example.com/httpdocs
/var/www/vhosts/xyz.example.com/httpdocs
Now we have to create Blogs for each Live Site, we are looking into Drupal Mutlisite Architecture for the same, so all Sites should point to same codebase, which would ease our maintenance tasks.
We have currently created symlinks for to main/default domain Site directory which is installed at blogs.example.com so symlink is created as
ln -s /var/www/vhosts/blogs.example.com/httpdocs/ /var/www/vhosts/xyz.example.com/httpdocs/blog
And created a folder under sites as sites/xyz.example.com.blog
But when we open the URL in browser we get "No input file Specified"
We are not sure if the above error is due to some issue in .htaccess, also we are consfused where to add htacess configuration related to MutliSite.
Any help would be appreciated.
As explained here your symbolic link shall be under /var/www/vhosts/blogs.example.com/httpdocs as the installed directory as well as the created sites folder. Try also to remove the end slash on httpdocs/ on your symbolic link:
ln -s /var/www/vhosts/blogs.example.com/httpdocs/ /var/www/vhosts/xyz.example.com/httpdocs/blog
to httpdocs only, like so:
ln -s /var/www/vhosts/blogs.example.com/httpdocs blog
or do it in 2 lines command:
cd /var/www/vhosts/blogs.example.com/httpdocs
ln -s . blog
Make sure also that CNAME of both xyz.example.com and blogs.example.com are the same and that the xyz.example.com is set as ServerAlias to blogs.example.com on your vhost. So you should get your site when point your browser to http://xyz.example.com/blog.
Once you have login to your new site as the admin, check or put the correct path for Public file system path under the following admin menu to sites/xyz.example.com.blog/files:
Home » Administration » Configuration » Media » File System
My configuration
- Mac OS 10.9
- XAMPP
- ProFTPD
- WordPress 3.8.3
Unlike most other posts on the internet for the same problem, I was not on some hosting website rather on a locally hosted instance on Mac.Everytime I tried to access the site, I got the error that the server was unable to locate the wp-content directory.
In macOS httpd server is executed as user "daemon".
Therefore you need to change ownership of htdocs to daemon user:
$ sudo chown -R daemon:daemon htdocs
After a few hours of tweaking around, I did the following
Delete previous installation of WordPress and install fresh copy
Set the permissions on wp-content directory via termina shell using the command chmod -R 777 wp-content. This sets the permission of all underlying files and folders as well
I went to this link and used the solution provided here - http://wordpress.org/support/topic/auto-update-failure-in-wordpress-27?replies=17#post-982487
Essentially, I added the following line at the bottom of my wp-config file - putenv('TMPDIR=' . ini_get('upload_tmp_dir'));
Vola!! it worked and I can now focus on more important things.