Possess a client who would like to move their Wordpress.com blog to their primary domain which has a Drupal installation. Basically add Wordpress to some "/blog/" directory around the server, maybe there is any conflicts using the htaccess ie Mod Rewrites etc?
Should you put the WordPress files inside the
/blog/ directory then no, there certainly should not be any htaccess conflicts.
What berkes indicates below (ie putting WordPress and Drupal in their own individual separate folders alongside) could be a perfect solution should you be beginning on your own.
However, it might alter the Web addresses of existing content, that you simply most likely do not want.
One factor you could do this is set them up alongside after which use mod-rewrite to create
example.com/blog visit the wordpress directory and other things visit the drupal directory.
By doing this all existing content would remain at the present Web addresses despite the fact that the drupal instalation had moved.
Observe that even this solution would prevent anything which Drupal attempted while using /blog path for from being visible, rather redirecting to WordPress.
It will likely be impossible to set up Drupal and Worpress in a single directory. Not just due to .htaccess issues, but additionally due to (potentially) conflicting files and libraries. Furthermore: your maintainance and upgrades is going to be come hell.
- I'd advice to make use of different virtual hosts. Anymore professional webhoster enables you to definitely define virtualhosts. Determining them is dependent around the server, setup, lfavour of OS and so on, and it is an entire subject by itself.
- Alternatively, you can produce a
/path/to/webroot/__blog__/directory. Advice you to definitely not put Wordpress under drupal (a /blog directory within the Drupal directory) nor to place Drupal under wordpress (a /content management systems directory within your Wordpress install. This can result in conflicts. Drupal might have an url /blog (it will!) which will conflict and wordpress could have a /content management systems url (it does not, but tend to have) which will conflict. Alongside, not inside each other.
- Another alternative is always to bridge one Content management systems using the other. This really is tough and sophisticated, but it might be easy to include wordpress in Drupal or vice-versa, given you've enough development and configuration some time and -experience.