I have been searching around the web for a solution but can't seem to find any to fix this situation. I can access the website through domain.com/joomla but not on the main domain without the /joomla.
(below are the two image to show the differences)
On my backend, the site is not offline, and I have at least 1 default article.
Could you please provide me with a new angle on how to solve this problem?
Thanks!
It's not working because you've installed it in a subfolder, if you want to view the website via domain.com then install joomla in the domain root folder.
You can also try this: .htaccess redirection to subfolder (masked)
Related
I created a site in Kentico 12 and using the live viewer was working fine. Now its started 404ing every time I try to go to the site either by the URL: localhost:8080/Kentico12_[sitename] or by viewing the site through the live site feature. I a new site and it does the same thing. Additionally, page preview 404s as well. I have tried changing domain alias' and URL patterns but it doesn't seem to work. If anyone has a solution or some useful documentation to point mee toward that would be appreciated.
I can get into the back end of the site no problem by going to http:localhost8080:/Kentico12_Admin
I can reinstall Kentico 12 if needed but would rather avoid that.
Reinstalling is not the answer. Make sure you have the site properly setup in IIS first. A simple setup is to set the root of the site in IIS to the root of your MVC site. Then under that main site, create a virtual application and set that to the root of the CMS directory and call that virtual application "cms".
Then navigate to localhost/cms and you should be directed to the Kentico login page. Once you've logged into the Admin interface, update your site's domains. The Site domain name should be localhost/cms. The Presentation URL should be http://localhost.
If after you've made those changes and you're still getting 404's we'll have to look into other possible issues maybe in your web.config.
Good day!
I have a problem with my site. I have used wordpress as my cms on plesk. Now, I have accidentally pressed 'publish site' on the prensence builder in plesk after which, my wordpress site is overlapped with the site that has been made using presence builder in plesk. I have no idea on how to get my wordpress site back. How can i disable the ones on the presence builder? Can I get my wordpress site back without installing it back? I really want my wordpress site back. Thanks in advance.
SiteBuilder's publish button copy SB's site files into web root folder of your domain, for example /httpdocs/
And sitebuilder's index.html just overlaps WordPess's index.php.
So you can just rename /httpdocs/index.html in to something like /httpdocs/index-sitebuilder.html and you should see now your WordPress site.
I have a website built with Wordpress that has been having permalink issues. A few days ago, I had added a simple file, named qr.php, that I dropped in at the root level (where the wp-content and wp-upload folders reside). It has a script that redirect to pages outside of my website depending on what type of device the user is using. Basically, some one on a Apple device gets redirected to an itunes page, and droid user to the droid app store, etc.
Could this non Wordpress page be causing issues? I have had static or html pages in amonst my root level files before, and never had an issue. I feel like the redirects may change this.
Rather than using the qr.php(cutom redirect file) in your wordpress site. You can use a plugin which will help to redirect the external links.
Some of the plugins which might help you to achieve your purpose are Device Redirect - WordPress Phone &Tablet Redirect , RedirectPlus - Wordpress Mobile Redirect Plugin.
See the screenshots, try demo and check whether it fits your requirement.
No, it dont cause any issue with permalink..
I am also using a wordpress website : abc.com and a php based software integrated to admin folder on root.. And I can access easily abc.com and abc.com/newfolder/abc.php
As always thanks in advance if you can help.
I'm seeing a very weird issue with a multisite. Currently it has the following multisites setup:
www.domain.com
www.domain.com/london/
www.domain.com/paris/
www.domain.com/berlin/
Each subdirectory site uses a different child theme (containing a few changes to css in each) of www.domain.com overiding theme.
The network sites each have the setup options for Siteurl and Home, which each reflect the setup of:
Siteurl:www.domain.com
Home:www.domain.com/london/
This works fine, but BREAKS the backend navigation for the /london/ website trying to force all wordpress links as www.domain.com/wp-admin rather than www.domain.com/london/wp-admin.
I changed the network setup of each website to the equivalent of:
Siteurl:www.domain.com/london/
Home:www.domain.com/london/
This fixes the navigation for the backend of www.domain.com/london/wp-admin but breaks all path files for calling anything from the parent theme and breaks all css/images in the backend of wordpress.
This is dricing me crazy! Anyone else seen anything like this before?
So the answer to this if anyone finds this was that our server was running NGINX without us realising which caused some pretty weird conflicts with the wordpress url re-writing. We simply turned it off and just run the server with stand alone Apache and it worked!
I have a main portfolio site hosted through MacHighway. My hosting package allows me to have two domains. I thought I'd register a new domain to experiment with some new things. So I bought a new domain, went into my main site's cPanel, registered it as an Addon Domain, and tried to install Wordpress on it. I got Wordpress working on it just fine, but then all of the links on my main site broke. So I deleted the files for the new site to see if that would help, but all of the links on my main site are still broken. The pages all say 'file not found.' Where did I go wrong? How can I fix this? I don't care about the new site at the moment. I just need to get my main site back the way it was. Help?
This is my site.
Nevermind. I visited Settings > Permalinks and everything works again.