Old: DocumentRoot /var/www/home/www/{sitename}
New: DocumentRoot /var/www/home/users/{user.id}/www/{sitename}
I copied all files including wp-core files from Old DocumentRoot to New DocumentRoot and checked the site is working.
However, when I install plugins, it uploads to Old DocumentRoot like /var/www/home/www/{sitename}/wp-content/plugins.
In order to fix this problem, I have tried these things.
Changed recently_edited’s path and the word count -> didn’t work
Added define( ‘WP_PLUGIN_DIR’, dirname(__FILE__) . ‘/wp-content/plugins’ ); -> didn’t work
How can I change the wp plugin upload directory to like /var/www/home/users/{user.id}/www/{sitename}/wp-content/plugins?
Thank you for your help in advance.
ich habe folgendes Problem:
Ich habe eine WordPress Seite installiert und dort das Document Root ge?ndert.
Danach konnte ich weder meine Seite, noch das Adminpanel ?ffnen.
Ich habe mich dann dazu entschieden, WordPress neu zu installieren, da
nicht wirklich viel Content auf der Seite war.
Ich habe die Anleitung von folgender Seite befolgt:
https://www.digitalocean.com/community/tutorials/how-to-install-wordpress-with-lamp-on-ubuntu-18-04#step-4-–-downloading-wordpress
Leider kann ich nachdem ich den Apache Webserver, die SQl Datenbank und WordPress installiert habe, die Installation nicht starten.
Wenn ich meine Seite unter https://example.de/wordpress ?ffne oder https://IP/Wordpress
folgenden Fehler:
<?php
/**
* Front to the WordPress application. This file doesn’t do anything, but loads
* wp-blog-header.php which does and tells WordPress to load the theme.
*
* @package WordPress
*/
/**
* Tells WordPress to load the WordPress theme and output it.
*
* @var bool
*/
define(‘WP_USE_THEMES’, true);
/** Loads the WordPress Environment and Template */
require( dirname( __FILE__ ) . ‘/wp-blog-header.php’ );
Ich habe bereits versucht alle Pakete die mit WordPress zu tun haben,
zu entfernen, jedoch scheint irgendwie noch eine Konfiguration zu sein, die das Problem verursacht. Die Pakete wurden alle mit dem Paramter “purge” entfernt.
Ich hoffe jemand kann mir bei dem Problem weiter helfen.
]]>I’m running WP on my own personal Linux server (LAMP installed).
Right now, I have it set to an internal access only, but soon plan to hook it to a domain name, etc.
My problem is, I cannot figure the correct combination of settings in Apache and WP to get what I like.
1. At this time, this is the only website I have, but I anticipate hosting other domains on this same server so want to get it right now. Future domains may or may not be WP.
2. I am running Gentoo linux as my OS.
3. I’m changing the URLs and IPs..but this will give an idea of my directory structure and what I”m trying to do.
Ok, I currently have my Apache set to document of let’s say:
This is in my default_vhost.include file.
DocumentRoot “/var/www/htdocs”
<Directory “/var/www/htdocs”>
Options -Indexes FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
</Directory>
In my 00_default_vhost.conf file I have an entry like this:
Listen 80
NameVirtualHost *:80
<VirtualHost *:80>
ServerName localhost
Include /etc/apache2/vhosts.d/default_vhost.include
</VirtualHost>
In my WordPress General Settings I have both WordPress and Site URL set to: https://192.168.7.13/wordpress
(again…URLs modified and just for example, but currently using only internal IP addresses so this is similar).
Now, when I put my browser at the url :
https://192.168.7.13/wordpress
As expected, I see my website, all images, etc. working just fine.
However, what I need to do, is have my website to be reached from the virtual root domain:
https://192.168.7.13
I’ve tried putting this in my VirtualHost markup:
<VirtualHost *:80>
ServerName localhost
Include /etc/apache2/vhosts.d/default_vhost.include
DocumentRoot /var/www/htdocs/wordpress
</VirtualHost>
And I *do* see my site…sort of….if I hit the URL:
https://192.168.7.13
I see the type, and my links..but the formatting is whacked.
I also tried changing the WP General Settings for Site Address to be the https://192.168.7.13 entry, leaving the WordPress Admin URL the old way. I’ve also tried changing the WordPress Admin URL…
Basically I can’t get the site to look right at the URL I want it to have..
I’ve been reading that I also likely need to update the database…I installed the “Better Search Replace”….but I’m not exactly sure what combination I need to do and which steps the order is..to change this.
I’m guessing I”d replace “192.168.7.13/wordpress” with “192.168.7.13”
But is this in conjunction with changing the DocumentRoot in my virtual host?
Do I also change this in my General Settings entries?
I see many examples of doing something similar to this, by copying your index.php and all to the root directory, but that’s not what I’m wanting to do. Again, there will likely be more sites on this host.
I’m wanting to make the current directory with the WP install into one single virtual host entry…where others may come later.
I think I’m close in the concepts, but am just missing something here.
Again..soon I will replace the IP address and local host with a real domain, but i”M trying to work out how to set up the virtual domain now before I put it live on the web and hook it to a real domain.
Thanks in advance!!
chilecayenne
]]>None of these sites will be load-balanced right now, but we want to keep our options open and so would like to keep them behind the BigIP.
Our servers are Red Hat Enterprise 5 and we are using the shipping Apache 2.2. They are multi-homed, with separate interfaces for the host itself and target for the BigIP vip.
I have tried variations on the default Apache config, including separate vhosts for the direct (hostname) and external (BigIP) urls.
Can someone give me a place to start in debugging this? Any suggestions would be welcome. Thanks.
]]>I installed my wordpress and modified the DirectoryRoot of apache to the proper folder. WordPress runs fine, but ftp-based plugin install/upgrade or built-in wp upgrades do not work because it can’t locate itself.
What do I need to change to help it out?
]]>See This: https://www.ads-software.com/support/topic/override-wildcard-sub-domains-on-wp-multisite-mediatemple-dv?replies=4
I want to use WP Multisite to run specific subdomains while other OSS software like Magento run other specific subdomains. The wildcard subdomains prevent this and my virtual host attempts failed to overide it. My solution is to define which specific subdoamins WP sholud run and leave all others alone. This has brought an issue so I realize its not the best solution.
1. How do I specify in my .htaccess that;
If HTTP_POST (or suggest a better server variable) says request is from shopping subdomain redirect to the shopping DocumentRoot where Magento is installed so Magento runs that request.
Will this work for ensuring requests to the shopping subdomain are not handled by WP but by whatever is in its documentroot.
Note: There is a physical subdomain for shopping not virtual
2. Do you see any conflicts between Magento and WP in such a situation
]]>WordPress Address: https://dougal.gunters.org/wordpress
Blog Address: https://dougal.gunters.org
The apache DocumentRoot for this vhost is: /var/www/vhosts/dougal.gunters.org
My permalink structure is: /blog/%year%/%monthnum%/%day%/%postname%
Which results in permalinks like: https://dougal.gunters.org/blog/2009/10/20/wordpress-2-9-media-embedding
I think this is confusing the Lockdown mode in Super Cache, because it wants me to make my wordpress subdirectory writable, but what it really needs is to have a blog subdirectory under my DocumentRoot.
Any ideas on how to handle this?
]]>