I have copied a live wp multisite install ( grabbed everything via ftp ) and installed it on my mac ( I am using MAMP PRO ).
I found that the main site works like a charm. the second site doesn't work at all. If you try to hit it, it ends up throwing a 404 and redirects to the homepage.
I have checked the .htaccess and the wp-config.php and they are correct. I haven't changed the domain ( using the same domain on my mac as on live )
The interesting bit is that I can reach the wp-admin of the subdirectory site.
http://domain.com - working
http://domain.com/subdirectoryinstall - not working
http://domain.com/subdirectoryinstall/wp-admin - working
Anyone has this happen before?
Oh if it makes any difference it was wordpress 3.0.1 ( yeah I know what you think ) and now upgraded to 3.9.1
Related
I have a brand new TYPO3 10.4 install with a bootstrap sitepackage.
My page tree is this
Home
-> Building Management
--> Building Rules
Home shows fine, but all of the lower pages throw a 404 using the speaking url's, even from autogenerated links in the menus. I can still navigate using index.php?id=2, but this is not enabled at all by default.
If I set the language link to /en/ (rather than /) then no pages work, not even the home page.
I built the same site on my development server with the same version of typo3 and the same site package and it works as expected, just not on the production. Any idea where to look for a solution? Here's a pic of the site pagesites-page
The .htaccess was a clue. What appears to have happened is that the .htaccess file was not updated during the TYPO3 install. We copied one from another working install of 10.4.4 and that fixed it. I think there is a step in the install process that checks if there is a .htaccess file, and if there is then it doesn't copy or insert the required changes. Once we copied this across everything worked fine.
I can't access my prestashop admin page (in localhost)?
When I enter into this page, it's shows this error!
How to fix this problem? Please help me.
Prestashop changes its admin folder to something like admin12fsg7wghdfgf. You need to go to folder where you installed prestashop and find that folder. And after that you could enter backend side by link similar to this http://localhost/prestashop/adminwt3452sdg
I had the same problem.
I even deactivate the antivirus and nothing fixed the problem.
Then what I did is to install the eCommerce in a Cpanel and over there all worked perfectly.
It's caused perhaps because Prestashop is tracking urls for his product's installations and of course this doesn't work in localhost...
I had a problem and it became alright after I downgraded the PHP version to the one recommended by Prestashop for the relevant version.
In my case, the PHP version was 7.2 and Prestashop 1.6. The admin page did not open, 500 Error.
I lowered the PHP version to 5.6. May be upto 7.0 it accepts.
I am also trying to deploy a ZendSkeletonApplication on a shared host but I am facing some problem regarding redirection. The problem is when a user try to login it gets stuck to /projectname/user/authenticate. It doesn't get redirected to dashboard after authentication.Unfortunately all i see is a white, empty page. Locally it worked perfectly Here it looks like Zend doesn't recognize that it should do anything with this url and redirecto to appropriate action.
Thanks in advance
The problem is presented by the new release of PHP. Try updating your version of php above 3.xx. I upgraded to the latest version of php in the hosting and the problem was solved. PHP 5
I have been using Coda and regular version of Mamp for local development for longtime without getting into this permission mess. I recently, upgraded to Mamp Pro and setup it with VHosts. I have a site example.com with it's root path set to /Users/john/Sites/example. I have set the owner and group to www in Mamp Pro.
The moment I got all this configured I started having problems with Coda. It keeps asking me the username and password to edit the local files at /Users/john/Sites/example. I guess I have to enable FTP on my Mac and then add a site in Coda to stop it asking me to enter username password for every single file. However, I have no idea on how to get this working. I am using Lion 10.7.2
Additionally, I have setup etc/hosts file for pointing example.com to 127.0.0.1
UPDATE: Though the accepted answer by #mini does not directly answer this question. It is still an elegant solution with seamless integration with Coda.
Consider using DesktopServer instead (along with Coda 2). Unlike MAMP, you can work on template theme files directly with WYSIWYG preview, LAN share for mobile device testing (with WordPress, -not just HTML sites), enables AirPreview to work with WordPress, copy, import/export to live sites, etc. Setup is easy as it manages your vhosts, database, and project files in about three mouse clicks:
http://www.youtube.com/watch?v=Pw9-F8etBPY
I have a DNN site (5.06) that I developed on a standalone machine running IIS7. When I copied the site to the production machine running IIS6 and enter the URL, such as www.site.com, I get a generic DNN error page with no additional information. However, if I add the default page, www.site.com/Default.aspx everything works fine.
The Friendly URL settings were never changed and I've verified Default.aspx is entered on the Documents tab in IIS6. The portal event viewer has no entry for the error page I get.
I'm nearly certain it has to do with migrating from IIS7 to II6; clearly I'm missing something here. Any ideas?
DNN has confirmed this is an error in 5.06, and will be addressed in a future update. That doesn't help me today, but I was able to work around the problem by adding the following to the Friendly URLs list:
Look for: .*/
Send To: ~/Default.aspx
I can't find the forum thread I was reading yesterday, but did find this one which also goes into detail on the issue: Error upgrading from 5.5.1 to 5.6.0
Pretty odd...
Double check PortalAlias table in your SQL server. Confirm www.site.com is in there.
Double check host headers in IIS6 has www.site.com
Make sure Default.aspx is in the documents area of IIS6 and set as the top default to run
Recycle your app pool
cross your fingers
Only thing I ever run into from IIS6 and IIS7 is in the app pool running in Integrated mode or classic... but that is usually as issue going from IIS6 to 7, not vice versa.
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have the correct machine key and connection strings. This is my last resort when DotNetNuke is being strange. I am running 10+ DNN sites at version 5.6.0 and I only encountered this issue once.