I have a wordpress blog installed in folder example.com/blog and now I want to use wordpress as CMS so I need to move wordpress to the root, the pages need to be in the root like example.com/page1 but I want that my blog posts will stay on example.com/blog/ with the defaults permalinks, example.com/blog/?p=123
How I do it via the web.config file on windows server?
Unless I'm misunderstanding it, your best bet would to probably just keep two separate installations of wordpress.
Related
I have a website example.com. I have a generic landing page on domain.com that I want to replace with a Wordpress site, but I do have several webpages that I care about. They are all static pages:
example.com/hello
example.com/goodbye
example.com/hello/canada
example.com/hello/usa
example.com/hello/mexico (you get the idea)
example.com/help
Wordpress question: I want to install Wordpress on example.com, while keeping my existing pages in tact:
example.com -- wordpress
example.com/blog/a-blog post -- a blog post from wordpress
example.com/blog/another-blog post -- a blog post from wordpress
example.com/category/something -- a wordpress category
And still having existing non-wordpress page at:
example.com/hello
example.com/goodbye
example.com/hello/canada
example.com/hello/usa
example.com/help
I will install Wordpress on an AWS EC2 instance. My website currently exists on another server. Should I keep the Wordpress install on a separate server? Or use a single server to serve both Wordpress and the static page? I use hover to manage my domain’s DNS settings. What is my best path forward?
Just placing the files in your root wordpress folder should work. And for simplicity's sake unless you have drastically different requirements of the static pages I would think they should be on the same server as the wordpress install.
Likely you'll want to separate out your styles/assets from your wordpress install (or use unique names) in which case each static page could have it's own folder matching the name of the page
/hello
style.css
hello.html
hello.js
Alternatively you can just create template files for each of your static pages. You don't have to use the loop, sidebar, header, from the rest of the site in custom page templates. This would allow the static pages access to optimizations affecting your whole site: SEO, security, load speed plugins, sitemaps.
Probably don't need to say but just make sure to backup your static pages before your wordpress install. You can likely bundle these with your wordpress theme. But --at least a few years ago-- the directory in which you install wordpress needed to be clear before successful installation.
I applied for a role and part of the application process requires me to build a WordPress site and make it live on a existing domain I own. This will assist the hiring company (example "WebCompany") to view and assess.
I have created the WordPress site locally and want to upload to my domain (e.g. www.mydomain.com.au) with a url extension like www.mydomain.com.au/webcompany.
Would it be as simple as just FTP the WordPress site to the root directory? Or do I need to set things up differently for it to work?
I recommend to install wordpress on your url with the same version, and use this plugin, I use it and helps even if you have info in your database, and your themes, all the stuff,
and then you have to active the plugins on the web, choose permalinks options.
WORDPRESS ALL-IN ONE PLUGIN
for the extension / what you mean really? you want wordpress on a /namefolder
because you can install wordpress in a folder and there's your extension, but if you have already wordpress installed on the public_html/ you can use multisite wordpress options.
Here is the info and I did it with this:
MultiSite Wordpress
I have a Magento site installed at the root of my domain and a Wordpress installed in a subdirectory. Currently I access my sites like this:
Magento: "domain.com"
Wordpress: "domain.com/blog"
I would like to be able to use Wordpress Pages seamlessly, without the "/blog" subdirectory showing in the url, such as:
Wordpress Page-X: "domain.com/page-x"
Note that I do want to keep the "/blog" subdirectory showing normally for blog posts etc... I just don't want it for Wordpress Pages.
Could anybody help on how to set that up? I was think tweaking the .htaccess would've work, but I can't find out how. Other solutions are welcome too. Thank you.
Magento provides you with an option to create custom URL rewrites in the backend (admin) you can find it here. This way you should be able to create rewrites. Also if you want to automate the creation of rewrites you can refer to the core_rewrites table in magento's database. Also this is a good read if you want to do logic based rewrites on the fly.
I am trying to merge my custom made directory site together with my wordpress site in one domain.
There seems to be issues with the url being redirected to my wordpress categories. How can i rewrite url in wordpress to compliment my directory site.
I don't think it's possible. Category, tag, page, post etc. slugs could collide with your directory names. You would have to either create a filter for WP to redirect specific URLs to your old content or modify your .htaccess file. Both methods are extremely complicated if you have a lot of pages, and overkill if you have only a few.
Why not migrate your old content to WP? Or if you don't want to do that, install WP into a subdirectory of your site, like /blog.
Have a client who wants to move their Wordpress.com blog over to their main domain that has a Drupal installation. If I add Wordpress to a "/blog/" directory on the server, will there be any conflicts with the htaccess ie Mod Rewrites etc?
Thanks.
If you place the WordPress files within the /blog/ directory then no, there certainly shouldn't be any htaccess conflicts.
Update :
What berkes suggests below (ie putting WordPress and Drupal in their own separate folders side by side) would be an ideal solution if you were starting from scratch.
However, it would change the URLs of all existing content, which you probably don't want.
One thing you could do is install them side by side and then use mod-rewrite to make example.com/blog go to the wordpress directory and anything else go to the drupal directory.
This way all existing content would stay at the existing URLs even though the drupal instalation had moved.
Note that even this solution would prevent anything which Drupal tried using the /blog path for from being visible, instead redirecting to WordPress.
It will be impossible to install Drupal and Worpress in one directory. Not only because of .htaccess issues, but also because of (potentially) conflicting files and libraries. Moreover: your maintainance and upgrades will be come hell.
I would advice to use different virtual hosts. Any more professional webhoster allows you to define virtualhosts. Defining them depends on the server, setup, lfavour of OS and so forth, and is a whole topic on its own.
Alternatively, you could create a /path/to/webroot/__cms__/ and /path/to/webroot/__blog__/directory. Advice you to not put Wordpress under drupal (a /blog directory in the Drupal directory) nor to put Drupal under wordpress (a /cms directory inside your WP install. This will lead to conflicts. Drupal may have an url /blog (it does!) that will conflict and wordpress may have a /cms url (it doesn't, but could have) that will conflict. Side by side, not inside one another.
Another alternative would be to bridge one CMS with the other. This is tough and complex, but it would be possible to include wordpress in Drupal or vice-versa, given you have enough development and configuration time and -experience.