StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POLaravel 4 controller routes not working due to apache2 configuration
primarykey
Id
17263458
data
AcceptedAnswerId
17332984
AnswerCount
4
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-06-23T17:37:52.013
FavoriteCount
1
LastActivityDate
2015-03-08T10:34:44.237
LastEditDate
2013-06-25T04:29:44.543
LastEditorUserId
1123590
OwnerUserId
1123590
ParentId
0
PostTypeId
1
Score
3
ViewCount
6388
LastEditorDisplayName
text
Body
I'm trying to set up laravel on my local server at home and I can't seem to get controller routes working eg: <pre><code>Route::controller('home','home'); </code></pre> This code works on a server I have at work and I've read a few forums about the issue which claim the issue is because apache2 isn't configured to look at the .htaccess files. I've been messing around with that for a while but I still can't seem to get anything to work. I went into /etc/apache2/sites-available and created my own config file called site1 which looks like this: <pre><code><VirtualHost *:80> ServerAdmin webmaster@localhost DocumentRoot /var/www/laravel/ <Directory /> Options FollowSymLinks AllowOverride None </Directory> <Directory /var/www/laravel/> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all </Directory> ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/ <Directory "/usr/lib/cgi-bin"> AllowOverride None Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch Order allow,deny Allow from all </Directory> ErrorLog ${APACHE_LOG_DIR}/error.log # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. LogLevel warn CustomLog ${APACHE_LOG_DIR}/access.log combined Alias /doc/ "/usr/share/doc/" <Directory "/usr/share/doc/"> Options Indexes MultiViews FollowSymLinks AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.0/255.0.0.0 ::1/128 </Directory> </code></pre> I then ran a2dissite default && a2ensite site1 and /etc/init.d/apache2 restart but nothing happened. Thanks for your help and let me know if I need to clarify anything. Turns out apache isn't even reading the .htaccess file. I purposely wrote some nonsense in it that should have caused an error and it didn't.
Tags
<php><apache><apache2><laravel><laravel-4>
Title
Laravel 4 controller routes not working due to apache2 configuration
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USGavin Sellers
UserOwnerUserId
1. USGavin Sellers
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POLaravel 4 controller routes not working due to apache2 configuration
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.