Wordpress Tutorials
- Wordpress
- Directory and file structure.
- Wordpress configuration
- Htaccess Configuration
- WP-CONTENT user playground
- Increase file size loading in phpmyadmin on localhost.
- Fatal error: Allowed memory size of x bytes
- wordpress Dashboard
- How to set local host domain or Virtual host
- Header, index and footer page.
- How to create wordpress Themes
- Html to wordpress themes
- Child Themes
- Increase Upload Max Filesize
- wp_enqueue_style & script
- How to make plugin
- Create Plugin
- Insert data into table using plugin.
- Show data from database
- Hook & Filter
- Template Or Custom page template
- Custom Login template
- How to show post on diffrent page.
- Custom widgit
- How to use contact form 7 plugin.
- Wordpress Database
- How to use Duplicator plugin
- How to fix Fatal Error: Maximum Execution Time Exceeded in WordPress
- How to debuggin mode on in wordpress
- Auto update plugin and themes
- How to Transfer WordPress
- How to change a WordPress site URL
- Top 10 issues in wordpress
- wordpress website link
Wordpress setting
Wordpress Function
wordpress top 10 problems
Important Links
htaccess
The .htaccess is a distributed configuration file, and is how Apache handles configuration changes on a per-directory basis. WordPress uses this file to manipulate how Apache serves files from its root directory, and subdirectories thereof. Most notably, WP modifies this file to be able to handle pretty permalinks. This page may be used to restore a corrupted .htaccess file (e.g. a misbehaving plugin).
File name : .htaccess
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
Multisite
If you activated Multisite on WordPress 3.5 or later, use one of these.Subfolder Example
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
SubDomain Example
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
link : https://codex.wordpress.org/htaccess
WP htaccess Control :-
you can also use htaccess plugin.
WP htaccess Control should now really be called WP htaccess and Rewrite Control. It provides an interface to customize the htaccess file generated by WordPress but also its permalinks (author, category, archives, pagination and custom taxonomies). Have a look at the screenshot for a clearer idea of the available options.
Features:
Customizing the htaccess file generated by WordPress;
Removing any custom taxonomy's slug base from permalinks;
Removing the category base from permalinks;
Removing the author base from permalinks;
Customizing the Author Permalink Base;
Customizing Paginated Permalinks (translate the "page" word on permalinks to your own language);
Customization (and canonization) of the Search Permalink Base;
Creation of Category, Author, Tag and Custom Taxonomy based archives (ex: "http://your-site.com/category/stories/2010/12", "http://your-site.com/author/admin/2010/12/page/2" and "http://your-site.com/tag/wordpress/2010/12"), this will also work if you've removed the base slug;
Maintenance mode.
Easy to use "Suggested htaccess" rules:
Jim Morgan's htaccess;
Disable directory browsing;
Disable and redirect image hotlinking;
Disable and redirect file hotlinking;
Force canonical url (WWW or non-WWW);
Limit maximum file upload size;
Protect wp-config.php file from access;
Protect .htaccess file from access;
Protect comments.php from spam bots coming from nowhere;
Set 500 error page;
Set 403 error page;
Use mod_gzip if available;
Use mod_deflate if available;
Set admin email on server generated error pages;
Disable ServerSignature on server generated error pages.
Download htaccess plugin zip files :- https://wordpress.org/plugins/wp-htaccess-control/
The .htaccess fi le is very powerful and can control more than just URL structure. For instance,
you can control PHP confi guration options using the .htaccess fi le. To increase the memory
allotted to PHP use this command:
php_value memory_limit 64M
This increases the memory limit in PHP to 64 MB. You can also increase the max fi le size upload
and post size:
php_value upload_max_filesize 20M
php_value post_max_size 20M
Now the maximum fi le size you can post from a form and upload is set to 20 MB. Most hosting
companies set these values to around 2 MB by default so these are settings that will be used often
for larger fi le uploads. Not all hosting companies will allow these values to be set in your .htaccess
fi le, and they could create an error on your website if that is the case.
The .htaccess fi le can also be used for security purposes. Using .htaccess allows you to restrict access to your website by IP address, essentially locking it down from anonymous visitors. To lock down your website by IP addresses, add the following code to your .htaccess fi le: AuthUserFile /dev/null AuthGroupFile /dev/null AuthName "Access Control" AuthType Basic order deny,allow deny from all #IP address to whitelist allow from xxx.xxx.xxx.xxx Replace xxx.xxx.xxx.xxx with any IP address that you want to grant access to your website. You can have multiple allow from lines so add as many IP addresses as you need. This allows access to your website only if you are using an IP address defi ned here. A more widely used option is to lock down your wp-admin directory. This means that only IP addresses you specify can access your admin dashboard URLs. This makes it much harder for anyone else to try to hack your WordPress back end. To accomplish this, create a separate .htaccess fi le in your wp-admin directory with the preceding code.