jcaynes
Forum Replies Created
-
Ipstenu,
Thank you for the clarification. The change was made, computer and XAMPP restarted and the issue is resolved.
I appreciate your assistance, but still don’t understand why it’s handled differently.
Thanks.
Ipstenu,
I know you aren’t getting paid to review my questions and respond to them. I’m sure your time is very valuable. I am simply trying to clarify answers so that they don’t seem like vague responses to me.
I understand the .htaccess file is different for a multisite.I am not clear how the httpd and override issues are handled differently from a multisite and single site and why the single sites without an .htaccess file works, but the one site with the same settings and a multisite .htaccess file does not. It seems odd. I’m trying to understand the logic.
As for the .htaccess file, I copied it from one of your multisite posts that identified what a complete .htaccess file is for a multisite. So, all but multisite working is quite perplexing.
If you’d like to take a break from my posts, I’m fine to wait for someone else to answer.
Thanks.
Thank you, Ipstenu,
Change it to allow from all? Or AllowOverride Yes? I’m not clear on this.
I was wondering why these things would be different for a multisite, but you were referencing the .htaccess file?
Thanks for your time.
Hi Ipstenu,
There are three places for this in the httpd.conf file, so it’s a bit confusing. I’m listing each as they appear and commented text for context of the use.
Why would this affect only a multisite?
First:
ServerName localhost:80#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot “D:/xampp/htdocs”#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the “default” to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>Second:
<Directory “D:/xampp/htdocs”>
#
# Possible values for the Options directive are “None”, “All”,
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that “MultiViews” must be named *explicitly* — “Options All”
# doesn’t give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.2/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks Includes ExecCGI#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be “All”, “None”, or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride AllThird:
# “D:/xampp/cgi-bin” should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory “D:/xampp/cgi-bin”>
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>Thanks for your assistance!
The httpd.conf file information was provided earlier, the other virtual host information is from my httpd-vhosts.conf file. Just to keep us on the same page 🙂
Hi Ipstenu, I think I should have clarified that I have four working sites under development with XAMPP. ParceledGardens is the only multi site. The other three sites are fine, the multi site is not. When I referenced the other three blogs, it was regarding the three other wordpress sites and not subdirectories of ParceledGardens.
My host file and httpd.conf file is set, as the other three XAMPP sites are working properly:
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost127.0.0.1 localhost
127.0.0.1 http://www.analyticallyspeaking.com
127.0.0.1 http://www.parceledgardens.com
127.0.0.1 http://www.jancaynes.com
127.0.0.1 http://www.organically.us
127.0.0.1 http://www.theartisanjewelry.com<VirtualHost *:80>
DocumentRoot “D:\xampp\htdocs”
ServerName localhost
</VirtualHost><VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot D:\_analytic
ServerName http://www.analyticallyspeaking.com<Directory “D:\_analytic”>
Order allow,deny
Allow from all
</Directory>
</VirtualHost><VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot D:\_artisan
ServerName http://www.theartisanjewelry.com<Directory “D:\_artisan”>
Order allow,deny
Allow from all
</Directory>
</VirtualHost><VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot D:\_jcaynes
ServerName http://www.jancaynes.com<Directory “D:\_jcaynes”>
Order allow,deny
Allow from all
</Directory>
</VirtualHost><VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot D:\_organic
ServerName http://www.organically.us<Directory “D:\_organic”>
Order allow,deny
Allow from all
</Directory>
</VirtualHost><VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot D:\_pgardens
ServerName http://www.parceledgardens.com<Directory “D:\_pgardens”>
Order allow,deny
Allow from all
</Directory>
</VirtualHost>All the other information is as provided earlier. I’m pretty sure the .htaccess is borked somehow, but can’t put my finger on it.
Forum: Networking WordPress
In reply to: Image path issues and confusionI found an old .htaccess file from October and overwrote the current one. I’m not sure what was written to it by 3.3 but that resolved the issue. Thanks for helping to isolate where the issue would be.
Forum: Networking WordPress
In reply to: Image path issues and confusionWhat is different from the MultiSite PHP and JS that is different from the single WordPress PHP and JS? I have not lost any functions from the single installs, all load images and have no issues. As I understand it, there isn’t much of a difference any more?
Forum: Networking WordPress
In reply to: Image path issues and confusionI use mod-rewrite and have changed the upload settings for all blogs including the multisite. From the information below, it appears based on that the httpd.conf file is allowing instructions to be written.
httpd.conf is a configuration file which is used by the Apache HTTP Server. It stores information on various functions of the server, which can be edited by removing or adding a number sign “#” at the beginning of the line, thus setting values for each directive.
The httpd.conf file can be located on any UNIX-based system that complies with the Filesystem Hierarchy Standard under the following path: /etc/httpd/httpd.conf.
This file, httpd.conf was once used in Microsoft’s Internet Information Services
There is a module, invented and originally written in April 1996, called mod_rewrite that is designed to provide a rule-based rewriting engine, based on a regular expression parser, to rewrite requested URLs on the fly. This module operates on the full URLs (including the path-info part) both in per-server context (httpd.conf) and per-directory context (.htaccess) and can generate query string parts on result. The rewritten result can lead to internal sub-processing, external request redirection or to an internal proxy throughput. It has been described as “voodoo,” and Brian Behlendorf of the Apache Group has said, “The great thing about mod_rewrite is it gives you all the configurability and flexibility of Sendmail. The downside to mod_rewrite is that it gives you all the configurability and flexibility of Sendmail.”[1]Forum: Networking WordPress
In reply to: Image path issues and confusionIstenu, if multisite worked prior to the 3.3 upgrade, wouldn’t that indicate the httpd.conf was set properly?
Forum: Networking WordPress
In reply to: Image path issues and confusionplantme.parceledgardens.com does not load images. That’s what happened.
Forum: Networking WordPress
In reply to: Image path issues and confusionIpstenu, the .conf files are server level files that I do not have access to. Perhaps you could explain why that would cause an issue with just one sub blog following the 3.3 upgrade?
Thanks.
Forum: Networking WordPress
In reply to: Image path issues and confusionHi Andrea_r, per previous posts, my .htaccess file was intact as agreed to by you and Ipstenu. I’m sure with all the posts read, it is difficult to keep track on a two page thread. It would be better if it were all on one page or there was a way to link the thread together.
I have deleted the headers because they aren’t working, so being blank would be correct. I use the same themes for all my wikis. wiki.parceledgardens.com, wiki.theartisanjewelry.com and wiki.analyticallyspeaking.com. The settings are all the same, with the one difference being wiki.parceledgardens.com is under multi-site.
As previously stated, I have tried default 2011 theme, but am unable to load my own header with it. I have tried two other themes with same lack of success.
Forum: Networking WordPress
In reply to: Image path issues and confusionI use a proprietary hosting control panel. Set up was simply adding the subdomain in the wordpress network admin panel, as it is a multi-site. It worked for the other subdomain, shop.parceledgardens.com. It worked for wiki.parceledgardens.com prior to the 3.3 upgrade. Following the 3.3 upgrade, I lost my pretty permalinks and can only use default permalinks. Following the 3.3 upgrade, I lost images on wiki.parceledgardens.com that work in the other primary and subdomain blog. Following the problem, I removed and re-added wiki.parceledgardens.com from the network admin panel. I have tried the default 2011 theme, which does load images, but adding my own images don’t work. As previously mentioned, my image directory map and .htaccess file appears to be in tact. I have checked phpmyadmin to review the blog settings, url, image directories and cannot find anything that would be problematic. At this point, I’ll probably deactivate the network feature and manually create the sub-blogs as I am unable to see what the issue is.
Forum: Networking WordPress
In reply to: Image path issues and confusionIpstenu, if you mean adding the subdomain and pointing a file to the subdomain in the shared hosting environment, I don’t believe that happens with the multi-site. If that were true, then neither of my subdomains would be working. And then my subdomain wouldn’t be working at at all rather than just having image issues. So, I’m still perplexed as to why images aren’t working on only one subdomain following the 3.3 upgrade.