Problems running locally

[Peter Knight]

Hi guys

I'm attempting to install PW locally for the first time.

I've created and connected to the database but when I visit my admin/manager URL, I get the following error

http://localhost:8888/procewsswire-test/wire/

Forbidden
You don't have permission to access /processwire-test/wire/ on this server.

The actual demo site is showing fine with the minimal site profile. This is a download from the dev branch of github.

Just wondering is it a folders permission? I don't think I can CHMOD locally?

[adrian]

Did you set your admin panel path to "wire" ?

I think that is likely the problem. I think you might need to manually correct this. If you open up PHPMyAdmin or similar and browse the pages table - you will need to change the name field for the row with id: 2

"processwire" is the default, but you could use "admin" or pretty much anything else, but apparently not "wire"

[Peter Knight]

No joy. I located the appropriate the table and indeed it was set to "wire" but changing it to "processwire" or "admin" has no result when I used that new directory within the URL.

Thanks anyway

Interesting bu the admin url is by "wire" by default when I unzip the latest gihub build

[Peter Knight]

I did a reinstall with a new database and left the Admin Login URL on the setup screen as "processwire".

After successful installation, I was given the new URL of /processwire/

Looking at my local files, the default folder called "wire" is still "wire" so I'm not suprised to get a 404 error.

Renaming that folder to "processwire" throws the original "forbidden" error.

I think I'll just install remotely for the moment or try the stable branch 

[cstevensjr]

 I did a reinstall with a new database and left the Admin Login URL on the setup screen as "processwire".

After successful installation, I was given the new URL of /processwire/

 

Looking at my local files, the default folder called "wire" is still "wire" so I'm not suprised to get a 404 error.

 

Renaming that folder to "processwire" throws the original "forbidden" error.

I think you are mixing things up.  The PW directories are /site and /wire.   The /processwire url in the setup script is for admin access purposes.  They are not the same thing.

Edited August 11, 2014 by cstevensjr

[Peter Knight]

I think you are mixing things up.  The PW directories are /site and /wire.   The /processwire url in the setup script is for admin access purposes.  They are not the same thing.

Ok, fair enough - thanks for clarifying.

Same issue though. Installation says I should visit /processwire/ to access the admin but browsing to this gives me a 404 on a local install.

[adrian]

Renaming that folder to "processwire" throws the original "forbidden" error.

I think I'll just install remotely for the moment or try the stable branch

Don't go renaming the wire folder. As cstevensjr says, the admin URL is not at all related to the name of that folder. The admin page in PW is just a page in the system and the URL is defined by that entry in the database that I pointed you to which is controlled by some .htaccess mod_rewrite rules. 

Same issue though. Installation says I should visit /processwire/ to access the admin but browsing to this gives me a 404 on a local install.

That is now a very different error to what you first received. Take a look here for help with this:

http://processwire.com/docs/tutorials/troubleshooting-guide/page3

[Peter Knight]

Cheers adrian. Understood. I've reverted the folder name back to the original name.

Re the URL you supplied, I can confirm that mod_rewrite is working. Unfortunately I can't make any htaccess chaneges this is a local install. 

Thanks for the help. I'll perform a remote install.

[adrian]

Cheers adrian. Understood. I've reverted the folder name back to the original name.

Re the URL you supplied, I can confirm that mod_rewrite is working. Unfortunately I can't make any htaccess chaneges this is a local install. 

Thanks for the help. I'll perform a remote install.

Why can't you make any htaccess changes on a local install? All you probably need to do is edit the .htaccess file that is at the root of your PW site and uncomment the first option:

RewriteBase /

[OrganizedFellow]

Are you developing on Windows?

What LAMP server are you using?

I do all my development locally. I have at least five separate ProcessWire installations on my Windows 7 desktop.

[Peter Knight]

My mistake - I *can* edit the htaccess file and have uncommented the appropriate line

RewriteBase /

So right now I am getting the error as follows. 

• Not Found
  The requested URL /index.php was not found on this server.

I presume there should be an index.php file in the root of /processwire ?

[Peter Knight]

Are you developing on Windows?

What LAMP server are you using?

I do all my development locally. I have at least five separate ProcessWire installations on my Windows 7 desktop.

MAMP 3.05 running on Mac OSX Mavericks

Might fire up the other Mac and see if I have the same issue and try one of the Windows machines too.

[SiNNuT]

A bit OT.

I always set up virtual hosts for every project or test install i do. This way the default .htaccess has never failed me and it saves headaches when deploying to live domains.

Installing into (sub)folders of localhost is not optimal to my taste.

[kongondo]

Mac installs: 

https://processwire.com/talk/topic/5797-setup-a-processwire-environment-on-a-fresh-macos-x-install/

https://processwire.com/talk/topic/4917-the-admin-cannot-be-reached-in-new-installation/

https://processwire.com/talk/topic/98-installing-on-mac-localhost-going-all-sorts-of-wrong/

https://processwire.com/talk/topic/6803-help-needed-for-local-setup-on-a-mac/

Edited August 11, 2014 by kongondo

[OrganizedFellow]

 presume there should be an index.php file in the root of /processwire ?

If "/processwire" is the root of where you extracted the following zip, then YES. It has an index.php file

http://processwire.com/download/

Upon initial extraction, you'll have this structure:

FOLDER
site-default
wire

FILE
.gitignore
COPYRIGHT.txt
htaccess.txt
index.php
install.php
LICENSE.txt
README.md

The folder 'site-default' automagically gets renamed to 'site' after installation.

After installation, you'll find your WORKING FILES here:

./site/templates/...

By WORKING FILES, I mean these are the ones you'll be working with 99.99% of the time.

During the installation, whatever name you give your "Admin Login URL" is how you would access your site back-end.

I always set up virtual hosts for every project or test install i do. This way the default .htaccess has never failed me and it saves headaches when deploying to live domains.

I do the same.

Live site = website.com

Test site = website.dev

Makes it SO much easier.

[pwired]

Hi Sparrow,

First go here:
https://processwire.com/talk/topic/4917-the-admin-cannot-be-reached-in-new-installation/#entry47998

Running on a Mac ?

Martijn did a great post here about this:

https://processwire.com/talk/topic/5797-setup-a-processwire-environment-on-a-fresh-macos-x-install/

If that did not help then continue here:

Can you open other pages on your local website ?
Have you links on them and do they at least work ?

Used sub-dir under your root when installing PW ?
There is a line in the .htaccess file that refers to "RewriteBase".
Uncomment this line and type your dir into it.

Check if your .htaccess is really working.
Type some random chars into the .htaccess to see if a 500 (?) page comes up

Try to revert back the .htaccess to its default with the changes in the VirtualHost only

Check your default Apache configuration. Has it turned off
 "AllowOverride" setting for e.g. /var/www,  ?

Check your VirtualHost declaration in httpd-vhosts.conf:

change names and paths in example to your local ones,

<VirtualHost *:80>
DocumentRoot "/Users/username/Test Site"
ServerName testsite.loc
<Directory "/Users/username/Test Site">
AllowOverride All
</Directory>
</VirtualHost>
 

=================================

Let us know what you have found.

[Nico Knoll]

Just take a look in the troubleshooting guide:

http://processwire.com/docs/tutorials/troubleshooting-guide/

http://processwire.com/docs/tutorials/troubleshooting-guide/page3

[Peter Knight]

Guys - thanks for all your help. 

I did a reboot of MAMP, rebooted my Mac and did a fresh install of PW and it's working now.

Appreciate all the help though.

I always set up virtual hosts for every project or test install i do. This way the default .htaccess has never failed me and it saves headaches when deploying to live domains.  

What are the benefits of a virtual host when developing locally? And whats the difference between running on MAMP or some localhost?

[marcus]

Guys - thanks for all your help. 

I did a reboot of MAMP, rebooted my Mac and did a fresh install of PW and it's working now.

Appreciate all the help though.

What are the benefits of a virtual host when developing locally? And whats the difference between running on MAMP or some localhost?

You can always simulate the production site domain situation, so you won't have to do fixes (Rewrite Base, etc.) for localhost/ProcessWire/project when you live domain is just yourwebsite.com.

You can take that even further and simulate server capabilities, for example Apache module versions and so on with Vagrant

[Martijn Geerts]

What are the benefits of a virtual host when developing locally?

Say you have a local 'domain' called 'mydomain.dev' then you can reach it in your browser at http://mydomain.dev, and the manager at http://mydomain.dev/processwire/. This way your local environment have the same url structure as the live situation. etc.

[SiNNuT]

You should read up about what localhost means. MAMP (which i haven't used, because i'm on Windows) is just a convenience package for having PHP, MySQL and Apache run on your computer, in essence a webserver with PHP and MySQL available. This (Apache) webserver serves pages on http://localhost/ , most of the time on port 80, so that would be http://localhost:80/ . Localhost is basically a shortcut to the IP-adress that represents your own system, IP 127.0.0.1
 
So MAMP also makes http://localhost available. This will have a set document root.
 
http://localhost[=docroot]/myproject[=subfolder]/
 
Sometimes this will cause problems with the rewritebase settings in the .htaccess file that comes with PW. So you need to change settings, and probably rechange when you put the stuff on a live domain, such as myproject.com.
This is maybe not a real big deal but there can be other disadvantages of developing locally with sub-folders of localhost. One that comes to mind is links that you insert via a Rich Text Editor.
 
Like the others have said, vhosts allow you to basically map a directory anywhere on your file-system to be the documentroot for a domain of your choosing.
 
For example:
http://myproject.development could be address that you could access in your browser while your project files could be anywhere.
 
Of course, MAMP, also allows for these kinds of setups. MAMP PRO seems to have built-in options. For regular MAMP there are enough guides on Google, for example:
http://sawmac.com/mamp/virtual/
http://foundationphp.com/tutorials/vhosts_mamp.php