When using the Views admin panel, it appears completely mispresented. Looking at the files being accessed, it turns out that the needed css files are not loaded. My Drupal installation is within a /drupal/ subfolder, and when the module is trying to access domain.com/sites/all/modules/views/css/views.css a 404 is received.
I tried browsing manually to domain.com/drupal/sites/all/modules/views/css/views.css and it works, therefore the file is there and can be accessed from the web.
The strange thing is that for other folders there is no problem, for example both domain.com/modules/user/user.css and domain.com/drupal/modules/user/user.css work. It seems like a problem with sites/ only...
I do not have CSS optimization enabled, and all folders within sites/ have a 755 permission. Is there some configuration setting I'm missing?
Apparently, the domain I'm concerned about is a parked domain (or whatever this is called) for another one, and contained in a subfolder of public_html. Drupal installation, thus, is a subfolder of that subfolder (say, /home/user/public_html/my_domain/drupal) and all requests for my domain are redirected via an .htaccess and MOD_REWRITE, to the Drupal subfolder. For some reason, it didn't have the sites/ in its regexp (modules/ and themes/ were...).
You may have incorrect vhost configuration. In order to check if this is the reason, try accessing the site without the vhost i.e. localhost/drupal and see if this works.
If it loads correctly, then you need to set up the correct document root:
<VirtualHost *:80>
DocumentRoot /www/drupal
ServerName domain.com
</VirtualHost>
Then restart apache.
For more information about how to set up vhost, visit http://httpd.apache.org/docs/2.2/vhosts/examples.html
Related
I have a server on which I want to run multiple wildcard vhosts, with their own modperl environment.
Each vhost needs to run it's own startup script to define custom include paths.
In a normal vhost configuration, I can do the following...
<VirtualHost *:80>
ServerName web1.myserver.com
Define ApplicationRoot /websites/web1
DocumentRoot ${ApplicationRoot}
PerlSetEnv PERL_DOC_ROOT ${ApplicationRoot}
PerlOptions +Parent
PerlPostConfigRequire /websites/lib/startup.pl
...
My startup.pl script can then use the PERL_DOC_ROOT environment variable to dynamically configure custom lib paths.
This works fine with multiple vhosts sections. They each have their own #INC defined, and everything resolves correctly.
Is there some way I can translate this to a wildcard vhost configuration. I'd like users to be able to access *.myserver.com, and it will use the hostname to figure out which documentroot to use, and will run the startup.pl to define lib paths based on this folder.
I know I can use something like this...
VirtualDocumentRoot /websites/%1/
to dynamically set the document root, but if I try to use %1 in any other declarations it is not understood. Also the startup.pl would need to run when the site is first requested, rather than when the config file is first loaded.
Is this possible at all? Or would I need to somehow dynamically rewrite the config files each time a new virtual directory is added.
I realised I'm overcomplicating it. I don't need to use wildcard vhosts. Since I'll be using Jenkins to create the vhosts directories, I can also get it to dynamically create config files to match.
I'm trying to look at Angularjs (going through Code School demo).
When I make changes to the template they are not reflected when refreshing in the browser. I have tried:
hard refreshing (and confirmed code 200 in the apache log)
deleting the browser cache (firefox)
Renaming the file on the server.
Opening in a different browser
However, copying the file to a new name on the server DOES have the changes be reflected.
regular HTML files that do not include the angular library update as normal.
Making a change to the javascript is reflected immediately (e.g. adding an alert('test')).
Is there something fundamental that I am missing here?
EDIT - Environment Details
Running on a Centos6.6 virtual box (Virtualbox) on a mac OS 10.10. Document room is /var/www/dev which is a symbolic link to /mnt/dev which I have mounted via the VirtualBox tools so I can edit the file directly on my mac
the VM config
Listen 10001
NameVirtualHost *:10001
<VirtualHost *:10001>
DocumentRoot /var/www/dev
<Directory />
Options +FollowSymLinks
AllowOverride None
</Directory>
</VirtualHost>
Take a look at this and see if the firefox answer by #hadaytullah solves your issues. I would also try it in Chrome. Probably using Angular's template caching somewhere.
This issue turned out to be a vboxsf issue as per the issue below. The changes made to the filesystem were not getting servered by apache.
https://github.com/yesodweb/wai/issues/315
Workaround: Turn sendfile off in httpd.conf
EnableSendfile off
The only way it worked for was this:
Go to firefox menu -> preferences -> advanced -> Network -> under Cached Web Content click on Clear Now.
I'm currently trying to install cake on a new site hosted on mediatemple/plesk on a shared ip. I have added the unzipped cake package to the httpdocs folder (../httpdocs/cake/), which is the server default for the site, as instructed in the cake documentation. It did not however bring me to the cake installation page, so as instructed in the cake documentation i reset the DocumentRoot for the site. The solution for document root that i found online for plesk was to set document root in vhost.conf and vhost_ssl.conf in the conf folder for the site i wanted to redirect. each of these files now has the following line of code (only code in the document):
DocumentRoot /var/www/vhosts/(mydomain.com)/httpdocs/cake/app/webroot/
As it still does not load to the cake homepage/installation page (instead i get the apache test page...) i have continued to search online and in these forums, but just keep coming up with reiterations of creating the vhost.conf and vhost_ssl.conf files as i did above (same line of code and everything)
manually directing my browser through the filepath to cake/app/webroot/ and cake/app/webroot/index.php returns only a blank page.
Is there any other way to get this to direct to the installation page correctly so that i can start to build?
DocumentRoot /var/www/vhosts/(mydomain.com)/httpdocs/cake/app/webroot/
i'd say this will not work.
Your index.php you'll need to access for cake is in "/var/www/vhosts/(mydomain.com)/httpdocs/cake/" if i'm correct.
You should remove the DocumentRoot and then browse to: mydomain.com/cake/index.php
there you should see the cake page
(this should be working before you try to set your DocumentRoot somewhere else)
I am trying to get my OSX MacPorts install of Apache to NOT show directory listings. I have tried various configurations of the "options" directive in the httpd.conf file with no luck. When I go to the site, it still lists the root directory (there is no index file at the moment.)
Apache has been restarted after each change.
There is no .htaccess file in the / directory, so there shouldn't be anything overriding.
This is driving me crazy!
So basically something is overriding your config. From the documentation of apache we can read that Options is can be placed in various context: server config, virtual host, directory, .htaccess.
httpd.conf is read first, so if You provided the configuration properly there, it means that it is overridden somewhere else
How did You do enter the options in the config ? In the most basic variant it should be.
<Directory /path>
Options -Indexes
</Directory>
Here what you should do:
check module configurations in modules for Options Indexes
check the main virtualhost definition, probably called default or 000-default
If it still does not help, add Options -Indexes to your virtualhost directly (provided you have not done it already). Or add it to the .htaccess file in your directory (allowing Options in .htaccess needs to be switched on)[as suggested in comments]
I am trying to install typo3 as per the instructions but I have a bit of a puzzle to solve.
It seems apache denies access to any files I try to access via any symbolic link in the site root directory. I have changed permissions from SymLinksIfOwnerMatch to FollowSymLinks and no joy.
I'm working on mac OSX (SL) and installing in my user's "Sites" directory. I can access any files in this CMS directory via the web browser just not anything through symbolic links.
I hope konsolenfreddy's comment was helpful already. I am trying to round things up here:
First check if the symlinks work from terminal and/or the filesystem in general.
Also, if you use absolute paths, the whole path from root to the file in question must be readable by the Apache user. *
If yes, check if the AllowOverride option is set for your webserver (or if applyable for the virtual host) For debugging you can set AllowOverride All in either apache2.conf, httpd.conf or in sites-available/default
If yes, check if FollowSymlinks is aktivated in any of the files responsible for your webroot, starting with apache2 working yourself down to the .htaccess files.
Try changing file permissions on the symlink file and the target directory (or files)
Try creating your own symlink and see what happens when you call it in the browser.
* Check this answer at askubuntu.com for more hints.
Ok I eventually solved it. In OSX the final file that governs access of sites installed in user directories is the last Include line in the apache2/conf/extra/httpd-userdir.conffile. Once I changed that my problems went away.
Thanks to all the people that replied my questions.