Is it possible to disable wordpress from a sub-directory?
Wordpress is currently installed in root.
So using wordpress' own CMS-functionality by going to Settings->General and changing Site-adress-URL wouldn't accomplish that since it would just move wordpress into a subdirectory. (which pretty much is the opposite of what i want to accomplish).
Is there any way to make wordpress ignore a specific subdirectory. Eg. Uploads/ to make me create standalone code there?
By default this should just work. The .htaccess file has a rule to ignore existing folders and files from rewrites. Creating a folder next to wordPress with custom code should work.
Related
In my wordpress website .htaccess has some strange redirection script, i removed the file but once the site is browsed the .htaccess file is automatically created with the strange script. in addition to that a folder named generall is also automatically creating even though we delete the folder. The folder has one php file and html file with strange scripts. Please help to resolve the hacking issue
You need to completely remove the infection from your site. Here's the easiest WordPress guide to follow: https://malcure.com/blog/security/the-easiest-guide-to-wordpress-malware-removal/
Your website still contains malware. You need to do a complete virus scan. You can use WordFence plugin to scan.
With these also try
1. Update all theme & plugins.
2. Do a manual update of your WordPress.
How can I upload a folder like a regular site and place it within a Wordpress folder but not have wordpress override the URLs for that particular folder.
Thanks
Your question is not really how you can do this, but why do it?
WordPress is overriding your URLs because of its own permalinks and rewrite rules in the .htaccess that handles the folder Wordpress is installed in and all subdirectories. Read https://codex.wordpress.org/htaccess
In order to place a "regular" site within a WordPress folder, you're going to have to work out some complex regex expressions https://stackoverflow.com/questions/tagged/regex and integrate them into Wordpress's own rewrite rules so both sites work. And then, when you change WordPress's own permalinks from admin and WordPress writes changes to .htaccess https://stackoverflow.com/questions/tagged/.htaccess, your own custom rules won't function anymore.
Directories below a directory with an .htaccess file will inherit those rewrite directives, so you can "negate" rewrite rules by putting a blank .htaccess file - or one with your own rules in it - in that folder. And this directory inheriting method is further controlled by server directives, if you have access to Apache httpd; which you won't, unless you're running your own server.
Again, why make things so complex? If you're going to use WordPress, integrate your content and site into WordPress. It is straightforward to integrate your own PHP and MySQL data into a WordPress site through the use of page templates. If you want a plain PHP/MySQL site in the same hosting area as WordPress, keep it separate.
I have a simple HTML microsite, which I want to put inside my wordpress website. For example: Wordpress website is: abc.com
I want to put my microsite inside this wordpress site. So URL becomes:
abc.com/microsite/
But, wordpress treats any url as its own. How can put "abc.com/microsite/" urls to Wordpress Ignore list. So that any pages inside microsite folder executes independently.
just put you folder 'microsite' in root(Where you find wp-admin,wp-content and wp-include folder). and
you are able to access the folder
"abc.com/microsite/ by this url
If you are still having issues with accessing the subfolder, try renaming the .htaccess to .htaccess-bak in order for WordPress to regenerate the file again. Understand that your website might temporarily go down.
I've found this solution to help in some cases, but I don't know exactly why, ergo I am not sure it will work. And if you feel uncomfortable editing the .htaccess file I suggest you learn more about it (as should I). It is a very powerful file and WordPress uses it a good deal.
P.S. The file is located in the same folder, WordPress' root folder where you find /wp-admin/, /wp-content/, etc. It is hidden by some hosting providers, but I've always been able to find them through FTP with the hosting companies I've used before.
I'm having a very basic problem: I'm trying to create a new theme for a wordpress installation locally on my computer.
I've created a styles.css and index.php file and put it in a folder in wp-content/themes. But it doesn't appear in the Wordpress themes page.
As a test, I made a change to the description of one of the existing themes (Twenty-Ten) in its style.css, and refresh the Wordpress themes page, but the old description continues to be shown. This suggests to me that I'm simply using the wrong folder, but that's not possible! Any ideas on this problem much appreciated.
UPDATE: In fact, even when I delete Twenty Ten from the Themes folder, it's still available as an option in the Wordpress backend, and I can activate it... Very strange...
G
I agree with your diagnosis. You are either looking at the wrong folder or in fact the wrong computer. There's no other way that you could change the theme to one that has been deleted.
I suggest that you confirm you are in the same universe you think you are in. Create a simple file localserver.txt in your WordPress directory and then confirm that you can access that file.
If you can't, you have your answer. You are somehow accessing a different location.
If you can access that text file, you need to go further and look to see if something like the site url setting is redirecting you to the live site, without you realizing it, when you access wp-admin.
Beyond that, I'd need to know more about your setup. Something like having www.example.com in your /etc/host file and not example.com can cause similar confusion...
Are you using Wordpress Multisite?
In that case you have to 'enable' that theme in the Network admin manager
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.