#How to Fix error in parent directory wordpress

[wandajouellette]

How to Install WordPress in a Subdirectory (Step by Step)

Do you want to install WordPress in a subdirectory? Installing WordPress in a subdirectory allows you to run multiple WordPress instances under the same domain or even a subdomain name. In this article, we will show you how to install WordPress in a subdirectory without affecting the parent domain name.

Subdomain vs Subdirectory? Which One is Better for SEO?

Normally, you would want to start a WordPress website on its own domain name (for example, wpbeginner.com). However, sometimes you may want to create additional websites on the same domain name.

This can be done by either installing WordPress in a subdomain (http://newebsite.example.com) or as a subdirectory (http://example.com/newwebsite/).

One question that we get asked is which one is better for SEO?

Search engines treat subdomains differently from root domain names and assign them rankings as a separate website.

For instance, search Engines consider WPBeginner and our WPBeginner Videos website as two separate websites.

On the other hand, sub-directories directly benefit from the domain authority of the root domain thus ranking higher in most cases.

One way to create separate WordPress sites in both subdomain or subdirectory is by installing WordPress multisite network.

However, if you want to keep two websites managed separately, then you can install different instances of WordPress. You can also use WordPress site management tools to set up a single dashboard for managing your multiple WordPress installations.

Requirements for Installing WordPress in Subdirectory

There are no special requirements to install WordPress in a subdirectory. If you already have a WordPress website in the root domain name, then you are good to go.

All top WordPress hosting companies make it very easy to install multiple WordPress websites using the same hosting account.

For instance, if you are using Bluehost, you can add a new WordPress website from your hosting dashboard.

However, please keep in mind that most shared hosting accounts have limited server resources. A sudden traffic spike on one of your websites will affect the performance and speed of all other websites on the same account.

If you are just starting out, then you can do that on shared hosting. Keeping in mind that you’ll need to upgrade to a managed WordPress hosting as your business grows.

That being said, let’s take a look at how to easily install WordPress in a subdirectory.

Step 1. Create a Subdirectory under The Root Domain Name

First, you need to create a subdirectory or a folder under the main website. This is where you will install WordPress files.

Connect to your WordPress hosting account using a FTP client or File Manager in cPanel.

Once connected, go to the root folder of your website. Usually it is the /public_html/ folder. If you already have WordPress installed in the root folder, then you will see your WordPress files and folders there.

Next, you need to right click and select ‘Create new directory’ from the menu.

You need to be careful when choosing the name for your subdirectory. This will be part of your new WordPress site’s URL and what your users will type in their browsers to reach this website.

For example, if you name this directory travel-guides then your WordPress website’s address will be:

http://example.com/travel-guides/

Step 2. Upload WordPress Files

Your newly created subdirectory is empty at the moment. Let’s change that by uploading WordPress files.

First you need to visit WordPress.org website and click on the download button.

Your browser will now download the zip file containing the latest WordPress software to your computer.

After downloading the file, you need to select and extract it. Mac users can double click the file to extract it and Windows users need to right-click and then select ‘Extract All’.

After extracting the zip file, you will see ‘wordpress’ folder containing all the WordPress files.

Now let’s upload these files to your new subdirectory.

Connect to your website using an FTP client and go to the subdirectory you created in the first step.

In the local files panel of your FTP client, go to the ‘wordpress’ folder you just extracted.

Select all files inside the folder and then upload them to your new subdirectory.

Step 3. Create New Database

WordPress stores all your content in a database. You need to create a new database to use with your new WordPress site installed in a subdirectory.

First, you need to login to the cPanel dashboard of your WordPress hosting account. Click on ‘MySQL Databases’ under the databases section.

Note: Your hosting dashboard may look different than the screenshot above. You simply need to locate the ‘Databases’ section.

On the next screen, enter a name for your new database and then click on the ‘Create Database’ button to continue.

Your cPanel dashboard will now create the new MySQL database. Click on the Go Back button to return to the Databases page.

Next, you need to add a username and password for the database.

Simply scroll down to the ‘MySQL Users’ section and provide a new username and password. Click on ‘Create User’ button to continue.

Next, you need to give this newly created user privileges to work on the database you created earlier.

Scroll down to ‘Add user to database’ section. Select your MySQL username and then select your newly created database.

Click on the Add button to continue.

Cpanel will now grant the MySQL user full privileges on your newly created database.

Step 4. Install WordPress

Now that everything is in place, you can go ahead and install WordPress. Simply visit the directory you created earlier in a web browser by typing the URL like this:

http://example.com/your-subdirectory-name/

This will bring up the WordPress installation wizard. First, you need to select the language for your WordPress website and click on the continue button.

Next, you will be asked to provide your WordPress database name, database username, password, and host. Enter the database details and click on the submit button.

WordPress will now connect to your database and you will see a success message like this:

Click on ‘Run the install’ button to continue.

On the next screen, you will be asked to provide a title for your website and choose an admin username, password, and email address.

After entering your website details, click on ‘Run install’ button to continue.

WordPress will now set up your website and will show you a success message:

You can now go ahead and login to your new WordPress website installed in the subdirectory.

Step 5. Fix Permalinks

If you have a separate WordPress install in the root directory, then the .htaccess files of your subdirectory will cause conflict. This will result in 404 errors on your website.

To solve this, you need to edit the .htaccess file in your subdirectory WordPress install. Replace the code inside your .htaccess file with the following code:

# BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase /your-subdirectory/ RewriteRule ^index.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /your-subdirectory/index.php [L] </IfModule> # END WordPress

Don’t forget to replace /your-subdirectory/ with your own subdirectory name.

We hope this article helped you install WordPress in a subdirectory. You may also want to see our ultimate step by step WordPress SEO guide for beginners.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Install WordPress in a Subdirectory (Step by Step) appeared first on WPBeginner.

from WPBeginner https://www.wpbeginner.com/wp-tutorials/how-to-install-wordpress-in-a-subdirectory-step-by-step/

[responsivesites]

New Post has been published on Website Design Naples Florida Webmaster

New Post has been published on https://vinbo.com/wordpress-5-5-beta-1/

WordPress 5.5 Beta 1

WordPress 5.5 Beta 1 is now available for testing!

This software is still in development, so it’s not recommended to run this version on a production site. Consider setting up a test site to play with the new version.

You can test the WordPress 5.5 beta in two ways:

Try the WordPress Beta Tester plugin (choose the “bleeding edge nightlies” option)

Or download the beta here (zip).

The current target for final release is August 11, 2020. This is only five weeks away. Your help is needed to ensure this release is tested properly.

Testing for bugs is an important part of polishing the release during the beta stage and a great way to contribute. Here are some of the big changes and features to pay close attention to while testing.

Block editor: features and improvements

WordPress 5.5 will include ten releases of the Gutenberg plugin, bringing with it a long list of exciting new features. Here are just a few:

Inline image editing – Crop, rotate, and zoom photos inline right from image blocks.

Block patterns – Building elaborate pages can be a breeze with new block patterns. Several are included by default.

Device previews – See how your content will look to users on many different screen sizes.

End block overwhelm. The new block inserter panel displays streamlined categories and collections. As a bonus, it supports patterns and integrates with the new block directory right out of the box.

Discover, install, and insert third-party blocks from your editor using the new block directory.

A better, smoother editing experience with: 

Refined drag-and-drop

Block movers that you can see and grab

Parent block selection

Contextual focus highlights

Multi-select formatting lets you change a bunch of blocks at once 

Ability to copy and relocate blocks easily

And, better performance

An expanded design toolset for themes.

Now add backgrounds and gradients to more kinds of blocks, like groups, columns, media & text

And support for more types of measurements — not just pixels. Choose ems, rems, percentages, vh, vw, and more! Plus, adjust line heights while typing, turning writing and typesetting into the seamless act.

In all, WordPress 5.5 brings more than 1,500 useful improvements to the block editor experience. 

To see all of the features for each release in detail check out the release posts: 7.5, 7.6, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, and 8.4.

Wait! There’s more!

XML sitemaps

XML Sitemaps are now included in WordPress and enabled by default. Sitemaps are essential to search engines discovering the content on your website. Your site’s home page, posts, pages, custom post types, and more will be included to improve your site’s visibility.

Auto-updates for plugins and themes

WordPress 5.5 also brings auto-updates for plugins and themes. Easily control which plugins and themes keep themselves up to date on their own. It’s always recommended that you run the latest versions of all plugins and themes. The addition of this feature makes that easier than ever!

Lazy-loading images

WordPress 5.5 will include native support for lazy-loaded images utilizing new browser standards. With lazy-loading, images will not be sent to users until they approach the viewport. This saves bandwidth for everyone (users, hosts, ISPs), makes it easier for those with slower internet speeds to browse the web, saves electricity, and more.

Better accessibility

With every release, WordPress works hard to improve accessibility. Version 5.5 is no different and packs a parcel of accessibility fixes and enhancements. Take a look:

List tables now come with extensive, alternate view modes.

Link-list widgets can now be converted to HTML5 navigation blocks.

Copying links in media screens and modal dialogs can now be done with a simple click of a button.

Disabled buttons now actually look disabled.

Meta boxes can now be moved with the keyboard.

A custom logo on the front page no longer links to the front page.

Assistive devices can now see status messages in the Image Editor.

The shake animation indicating a login failure now respects the user’s choices in the prefers-reduced-motion media query.

Redundant Error: prefixes have been removed from error notices.

Miscellaneous Changes

Plugins and themes can now be updated by uploading a ZIP file.

More finely grained control of redirect_guess_404_permalink().

Several packaged external libraries have been updated, including PHPMailer, SimplePie, Twemoji, Masonry, and more!

Keep your eyes on the Make WordPress Core blog for 5.5-related developer notes in the coming weeks, breaking down these and other changes in greater detail.

So far, contributors have fixed more than 360 tickets in WordPress 5.5, including 157 new features and enhancements, and more bug fixes are on the way.

How You Can Help

Do you speak a language other than English? Help translate WordPress into more than 100 languages!

If you think you’ve found a bug, please post to the Alpha/Beta area in the support forums. We would love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac. That’s also where you can find a list of known bugs.

Props to @webcommsat, @yvettesonneveld, @estelaris, and @marybaum for compiling/writing this post, @davidbaumwald for editing/proof reading, and @cbringmann, @desrosj, and @andreamiddleton for final review.

Original source: https://wordpress.org/news/2020/07/wordpress-5-5-beta-1/

[pixelproductions]

How to Fix the 9 Most Common WordPress Errors

WordPress error… The worst way to start a Google search – learn how to fix the 9 Most Common WordPress Errors here.

WordPress is the most used CMS on the planet and powers around 29% of the global internet. It is the first choice for millions of people, including developers, when they need to create an SEO optimized website, eCommerce site or blog. It is also the best tool to take your business or brand to your targeted audience.

With so many positive factors, there are certain “common errors” that many people run into on WordPress. This article covers the 9 most common WordPress errors and more importantly, how to fix these common WordPress errors.

1. Error establishing a database connection WordPress

This is a pretty terrifying error message to see when working with WordPress. It will break your site and can even make it pretty hard to access the admin in most cases. Chances are that you’ve accidentally done something to break the connection between your WordPress website and the database that holds all your information.

Finding and correcting an error establishing a database connection in WordPress is a total pain in the ass.

If you’re managing your own site — you don’t want to do this.

It is far better to take a preventative or at least prepared course of action by using a WordPress host that will resolve the issue for you; such as WP Engine.

If you have already run into this issue and need to resolve it yourself, walk through these steps on Kinsta’s blog.

2. Locked out of WordPress admin

If you have found that you have been locked out of your WordPress — the first thing that you need to do is try to recover your password available from the given WordPress login screen.

In the case that you don’t receive the reset email, well, then there could be one of several issues that will need troubleshooting. Lost admin privileges can range from simple to pretty complex, but the folks at mythemeshop have put together a great video to help you straighten it out:

3. WordPress Stuck in Maintenance Mode

Chances are that if you’re seeing this message you just updated a whole bunch of plugins on your WordPress site. It’s tempting to update everything at once, but you’ll quickly find this can cause problems.

If your website is stuck in maintenance mode, it means the .maintenance file was left behind after updates were performed. To fix the issue, you can simply remove the .maintenance file. The easiest way to do this is via SFTP.

In the document root of your website, there will be a file named .maintenance. Right-click the .maintenance file in the list, and select to delete or remove it.

If you can’t locate this file or the .maintenance file seems to be missing, please contact your hosting company.

4. WordPress 404 error Page or Post Not Found

The main cause of this error is the .htaccess file.

There are actually several variations of this error, but they all mean that a page can’t be found.

In 99% of such cases, these problems will disappear just by making some simple clicks on the save changes button on the Permalinks Settings page found on your WordPress Admin dashboard. This will force WordPress to rewrite the .htaccess file generally fixing the errors.

If you are getting the 404 error on all the WordPress pages but not the home page, you should fix the problem using the following steps:

Log into the dashboard

Click on ‘settings’ and then on ‘permalinks’

Click on ‘select the default setting’

Click on ‘save’

Now revert the settings back to previous form

Click on ‘save settings’

If this does not work, you will need to edit your .htacess file with new code by resetting the rewrite rules of the file .htaccess. But this will require that you access your WP site using an FTP server.

Follow these steps to set up an FTP client:

Download an FTP client (if you don’t already have one, click here for a list of the best)

Open the FTP client

Enter your website’s name

Enter your domain name in the ‘host’ section

Leave the ‘port’ section blank

Select FTP for ‘protocol’

Select plain FTP for ‘encryption’

Select normal as the ‘logon type’

Then enter your control panel’s username and password

click on ‘connect’ for connecting the FTP

Follow these steps to reset the rewrite rules:

Open your WP site’s root directory within the FTP client

Click on ‘server’

Select the option ‘force showing hidden files’ (this is important for showing all the hidden files because the .htaccess file may also be hidden by default.

Right click on the .htaccess file

Click on ‘file permissions’

Now you should make the .htaccess file writable.

*This can be done by using the following steps: (it can be risky editing your htaccess file, if you don’t feel comfortable doing this contact your hosting provider or a developer).

Enter the value 666

Click on ‘save’

Click on ‘refresh’

Go to WordPress and open ‘permalink settings’

Click on ‘save changes’

Go back to the FTP client and make changes to the .htaccess’ file permissions to 644

Refresh the client

5. WordPress White Screen PLEASE HELP ME!

This is the most dreaded error found in the WordPress community and is also referred to as the White Screen of Death or WSoD. When this error occurs, you won’t see an error message stating the reason. Oh, and you’ll be locked out of your WordPress admin — because that’s always helpful.

Again, this is the type of error where having the right WordPress hosting makes a huge difference.

Why?

Because the simplest and quickest way to resolve this problem is to have the ability to “roll-back” to a recently saved back up point.

If restoring your website is not an option, you’re most likely going to have to walk through a series of time consuming steps to figure out the culprit and fix the issue. If you have to do that, click here, for Kinsta’s Detailed Guide on this process.

6. An Automated WordPress Update Has Failed

It is important to keep WordPress updated always.

Most of the time, it will update automatically and everything goes as it should, but every once-in-a-while you do run across a failed auto-update.

It could be from something as stupid as an interrupted internet connection or also very commonly caused by file permissions. In case like the latter you can even run into the dreaded WSoD, or notice some warning errors.

The easiest fix:

1. Delete your maintenance file as illustrated in Step 3 Above.

If that fails, click here, and follow the steps outlined.

7. Issues in image uploading

The image upload issue in WordPress is typically caused by incorrect file permissions. Your WordPress files are stored on your web hosting server and need specific file and directory permissions to work.

Wrong file permissions prevent WordPress from reading or uploading file on the hosting server. You may get the following error when uploading image file:

‘Unable to create directory wp-content/uploads/2019/04. Is its parent directory writable by the server?’

For complete instructions on resetting your file permissions and resolving common WordPress image upload issues – Click Here.

8. WordPress 403 Forbidden error

The WordPress 403 Forbidden error is the consequence of a server refusing a request due to a lack of proper permissions. Therefore, it makes sense to start your troubleshooting by checking whether your WordPress files have the correct permissions.

I really hate this, because typically you end up spending more time trouble-shooting the issue rather than fixing the issue.

I hate to say it again, but in this scenario — I would opt for the roll back to your most previous back up point.

If you can’t do that then watch this video from WP Beginner:

9. Syntax error

Sometimes, when you are changing the code of WordPress, it might result in different syntax errors. Fortunately, WordPress will inform about the file that caused the error and locates the line has an error in the code. Just making the right alterations will be enough to fix the issue.

Other times this error can keep you from making any edits or updates to your site, but don’t worry — this can be fixed relatively easily. Just watch this video:

Final thoughts

WP is the strong platform but just like any software platform — there’s opportunity for error. The above errors are the common ones and by now you might have known to fix them to make efficient use of them.

[siliconwebx]

How to Fix Image Upload Issue in WordPress (Step by Step)

Are you facing image upload issues on your WordPress website? For most beginners, image upload errors can be quite confusing because they can appear without you doing anything different.

Failure to upload images is one of the most common image issues in WordPress. Luckily, it is quite easy to fix, and you can do it yourself.

In this article, we will show you how to easily fix the image upload issue in WordPress. We will also explain what causes this issue, and how you can prevent it in the future.

What Causes The Image Upload Issue in WordPress

The image upload issue in WordPress is typically caused by incorrect file permissions. Your WordPress files are stored on your web hosting server and need specific file and directory permissions to work.

Wrong file permissions prevent WordPress from reading or uploading file on the hosting server. You may get the following error when uploading image file:

‘Unable to create directory wp-content/uploads/2019/04. Is its parent directory writable by the server?’

Another sign of this issue is that your images may disappear from the media library.

My site was working fine before? Who changed the file permissions?

This could happen due to a number of reasons. A misconfiguration on your shared hosting server can sometimes change those permissions without you doing anything.

For example, your web hosting provider ran an upgrade which unexpectedly changed file permissions.

If everything else is working fine on your website, then you can simply apply the correct file permissions to fix the image upload issue.

That being said, let’s take a look at how to set correct file permissions to fix image upload issues in WordPress.

Fixing Image Upload Issue in WordPress

You will need to use an FTP client to change file permissions.

First, connect to your website via FTP and then go to /wp-content/ folder. Inside, you’ll find the uploads folder, which is where WordPress stores all your media uploads including images.

Now right click on the uploads directory and then select File Permissions.

This will bring up the file permissions dialog box.

First, you will need to set file permissions for the uploads directory and all the subdirectories inside it to 744.

To do that, enter 744 in the numeric value box, and then check the box next to Recurse into subdirectories option. Now click on the ‘Apply to directories only’ radio button.

Click on the OK button to apply these changes. Your FTP client will now start applying file permissions to the directories.

Note: If setting directory permissions to 744 does not seem to solve your problem, then try 755.

In the next step, you will need to set file permissions for all the files in the uploads directory.

To do that, right click on uploads directory and select file permissions. In the file permissions dialog box, change the numeric value to 644.

Check the box next to Recurse into subdirectories. Lastly, you need to click on ‘Apply to files only’ radio button. Click on the OK button to apply these changes.

The FTP client will now change the permissions for all files inside the uploads folder. Once it is done, you can go back to your WordPress admin area and try uploading images again.

Note: if you don’t know how to use a FTP client, then you can also use the file manager provided by your WordPress hosting company. Since the screenshots will vary from each host, you will need to talk to their support to find instructions.

We hope this article helped you fix the image upload issue in WordPress. You may also want to see our article on how to optimize image SEO to get more organic traffic to your website.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Fix Image Upload Issue in WordPress (Step by Step) appeared first on WPBeginner.

😉SiliconWebX | 🌐WPBeginner

[sheilalmartinia]

How to Fix Image Upload Issue in WordPress (Step by Step)

Are you facing image upload issues on your WordPress website? For most beginners, image upload errors can be quite confusing because they can appear without you doing anything different.

Failure to upload images is one of the most common image issues in WordPress. Luckily, it is quite easy to fix, and you can do it yourself.

In this article, we will show you how to easily fix the image upload issue in WordPress. We will also explain what causes this issue, and how you can prevent it in the future.

What Causes The Image Upload Issue in WordPress

The image upload issue in WordPress is typically caused by incorrect file permissions. Your WordPress files are stored on your web hosting server and need specific file and directory permissions to work.

Wrong file permissions prevent WordPress from reading or uploading file on the hosting server. You may get the following error when uploading image file:

‘Unable to create directory wp-content/uploads/2019/04. Is its parent directory writable by the server?’

Another sign of this issue is that your images may disappear from the media library.

My site was working fine before? Who changed the file permissions?

This could happen due to a number of reasons. A misconfiguration on your shared hosting server can sometimes change those permissions without you doing anything.

For example, your web hosting provider ran an upgrade which unexpectedly changed file permissions.

If everything else is working fine on your website, then you can simply apply the correct file permissions to fix the image upload issue.

That being said, let’s take a look at how to set correct file permissions to fix image upload issues in WordPress.

Fixing Image Upload Issue in WordPress

You will need to use an FTP client to change file permissions.

First, connect to your website via FTP and then go to /wp-content/ folder. Inside, you’ll find the uploads folder, which is where WordPress stores all your media uploads including images.

Now right click on the uploads directory and then select File Permissions.

This will bring up the file permissions dialog box.

First, you will need to set file permissions for the uploads directory and all the subdirectories inside it to 744.

To do that, enter 744 in the numeric value box, and then check the box next to Recurse into subdirectories option. Now click on the ‘Apply to directories only’ radio button.

Click on the OK button to apply these changes. Your FTP client will now start applying file permissions to the directories.

Note: If setting directory permissions to 744 does not seem to solve your problem, then try 755.

In the next step, you will need to set file permissions for all the files in the uploads directory.

To do that, right click on uploads directory and select file permissions. In the file permissions dialog box, change the numeric value to 644.

Check the box next to Recurse into subdirectories. Lastly, you need to click on ‘Apply to files only’ radio button. Click on the OK button to apply these changes.

The FTP client will now change the permissions for all files inside the uploads folder. Once it is done, you can go back to your WordPress admin area and try uploading images again.

Note: if you don’t know how to use a FTP client, then you can also use the file manager provided by your WordPress hosting company. Since the screenshots will vary from each host, you will need to talk to their support to find instructions.

We hope this article helped you fix the image upload issue in WordPress. You may also want to see our article on how to optimize image SEO to get more organic traffic to your website.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Fix Image Upload Issue in WordPress (Step by Step) appeared first on WPBeginner.

from WPBeginner https://www.wpbeginner.com/wp-tutorials/how-to-fix-image-upload-issue-in-wordpress/

[bloggerterminal]

Unable to create directory uploads/2018/11. Is its parent directory writable by the server?

Unable to create directory uploads/2018/11. Is its parent directory writable by the server?

How To Fix The Unable To Create Directory Error In WordPress

If you are seeing any of the following errors when you try to upload/import media into WordPress’s media library then this tutorial is for you. It will show you how to fix this annoying error.

Unable to create directory wp-content/uploads

Unable to create directory /wp-content/uploads/ Is its parent directory writable by the server?

Un…

[bestfile24]

Torrent Calligra Suite 2.9.7 be Repack

New Post has been published on https://bestfile24.com/linux/office-and-business/torrent-calligra-suite-2-9-7-be-repack/

Torrent Calligra Suite 2.9.7 be Repack

Calligra Suite is an open source Office Suite which comes packed with features. It currently works best on Linux, though: the OS X and Windows builds are variously described by the developers as “preliminary”, “highly experimental” and “unstable”, so you can download and try the suite, but should expect problems.

If you’re happy to try the suite anyway, though, this is what you’ll find.

Words is the Calligra word processor. It can open Microsoft Word DOC and DOCX files, ODT/ ODM documents and assorted other formats, and can save as ODT, ODM, EPUB, HTML and PDF, amongst others. And there’s a similar level of Office compatibility elsewhere, so Sheets (the spreadsheet application) can read XLS/ XLSX files, and Stage (the presentation tool) can handle PowerPoint documents.

Other productivity tools on offer here include Flow for flow charting and diagrams, Plan to handle your project management needs, while Kexi provides a visual way to create and manage databases.

And if you’re just feeling creative then you also get Karbon, a capable and extensible vector drawing tool, and Krita for painting and sketching.

How does this all feel in real life? It really does depend on your platform. The Linux builds work well, but when we tried the suite on Windows it was a very different story, with all kinds of odd problems appearing (much as the developers warned, to be fair). Words wouldn’t launch at first, for some reason. Application windows couldn’t be resized. Poorly chosen colour schemes made it extremely difficult to read some menus. The Help system just displayed errors about missing files, and so it went on.

Calligra is certainly ambitious, then, and if you’re running Linux then it already provides plenty of Office-compatible power. If you’re running Windows, though, we’d stick with OpenOffice, instead.

Version 2.9.7 changes include:

  Removed a number of memory leaks in common code

Properly set normal default paragraphstyle as parent to footnote/endnote default ones

Fix copying text from inside a table cell without copying the entire cell (bug 350175)

Optimalization of table cell formatting

Fix: pressing Backspace in some cases didn’t delete the selected table (bug 350426)

Fix: Inserting a variable when having a selecion should overwrite the selection (bug 350435)

Fix: Pasting into the before-table-paragraph breaks it (bug 350427)

Make the final spell checking markup could be drawn the wrong way giving some weird visual glitches (bug 350433)

Fix writing direction button not working the first time in some cases. Changed the way of detection the current direction. (bug 350432)

Make icon size of the toolbox configurable (right-click on the toolbox to select a new size) (bug 336686)

Add a couple smaller toolbox icon sizes (14 pixels)

Make the default toolbox icons 14px since that looks closest to what they were before

Update tool tips to include keyboard shortcut (tool tips will automatically change with changes to shorcuts) (bug 348626)

Make the default size of the toolbox buttons dependent on screen resolution

Create subfolders for presets (related bug 321361)

Initialize colors to black, as per docs

Improved memory usage (use vectors)

Set the full file name as default directory in file dialogs

Supported Keywords: Get Calligra Suite 2.9.7 Download Calligra Suite 2.9.7 How to get Calligra Suite 2.9.7

Check out our other profiles: Twitter -> https://twitter.com/bestfile24 Plurk -> https://www.plurk.com/bestfile24 Tumblr -> https://www.tumblr.com/blog/bestfile24 Vk -> https://vk.com/id484318694 Google+ -> https://plus.google.com/u/0/111792510074743799172 Wordpress -> https://bestfile24.wordpress.com/

[siliconwebx]

Why You Can’t Find .htaccess File on Your WordPress Site

Are you having trouble finding the .htaccess file in WordPress? We are often asked by beginners ‘Where is my .htaccess file?’ and ‘Why I cannot find it on my WordPress site?’.

Sometimes you may need to edit the .htaccess file or delete it to fix a common WordPress errors. In this article, we will explain why you can’t find .htaccess file on your WordPress site, and how to easily locate it.

What is .htaccess file?

The .htaccess file is a server configuration file which tells your server how to handle certain things on your website. Like how to redirect users, password protect admin area, or protect some directories, etc.

It is located in your WordPress site’s root folder. WordPress uses it to manage redirects and permalinks.

The .htaccess file is an incredibly powerful configuration file and can be used to do a lot useful things. See our article on the most useful .htaccess tricks for WordPress for some examples.

Why I Can’t Find .htaccess File?

There are two common reasons for not finding the .htaccess file in your website’s root folder. It’s either hidden by your file manager software, or it doesn’t exist at all.

We will explain both of them with solutions.

1. Your FTP Client is Not Showing Hidden Files

The dot before the htaccess file name indicates that it is a hidden file. By default, when you connect to your WordPress hosting server using an FTP client, it will not show the hidden files.

To make hidden files visible, you will need to change your FTP client settings.

For example, in FileZilla, you can find the option under ‘Server » Force showing hidden files’ menu.

If you are using the File Manager app in cPanel, then you will find the option to show hidden files before launching the app.

For other FTP clients, you will find the option to show hidden files in app settings or preferences menu.

After enabling this option, you would be able to view all hidden files including .htaccess file for your WordPress site.

2. The .htaccess File Doesn’t Exist

The second most common reason for missing .htaccess file is that your WordPress site has not generated it yet.

WordPress automatically generates .htaccess file because it is required to properly redirect permalinks.

If your .htaccess file is missing, then the first thing you need to do is to visit Settings » Permalinks page and click on ‘Save Changes’ button without changing anything.

WordPress will now try to generate the .htaccess file for you.

On some rare occasion, WordPress may not be able to generate the .htaccess file due to file permissions issue.

In that case, it will show you a message at the bottom of the Settings » Permalinks page, saying that the ‘.htaccess file is not writeable’.

You will need need to manually create the .htaccess file and add the required code inside it.

Simply copy and paste this code in a text editor like Notepad. After that, you need to save it as .htaccess file on your desktop.

Now connect to your website using an FTP client and upload the .htaccess file from your desktop.

If you get an error while uploading the file, then you need to change the file permission for your root directory.

Let’s suppose all your WordPress files reside under /home/johnsmith/public_html/ directory.

This makes public_html folder your root directory. You need to go to its parent directory and right click on the public_html folder. Select File Permissions, which will open a file permissions dialog box.

Now enter 755 into the file permission dialog box and then try to upload your .htaccess file to the public_html folder.

We hope this article helped you find .htaccess file on your WordPress site. You may also want to see our WordPress troubleshooting guide to learn how to diagnose and fix WordPress issues all by yourself.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post Why You Can’t Find .htaccess File on Your WordPress Site appeared first on WPBeginner.

😉SiliconWebX | 🌐WPBeginner

[sheilalmartinia]

Why You Can’t Find .htaccess File on Your WordPress Site

Are you having trouble finding the .htaccess file in WordPress? We are often asked by beginners ‘Where is my .htaccess file?’ and ‘Why I cannot find it on my WordPress site?’.

Sometimes you may need to edit the .htaccess file or delete it to fix a common WordPress errors. In this article, we will explain why you can’t find .htaccess file on your WordPress site, and how to easily locate it.

What is .htaccess file?

The .htaccess file is a server configuration file which tells your server how to handle certain things on your website. Like how to redirect users, password protect admin area, or protect some directories, etc.

It is located in your WordPress site’s root folder. WordPress uses it to manage redirects and permalinks.

The .htaccess file is an incredibly powerful configuration file and can be used to do a lot useful things. See our article on the most useful .htaccess tricks for WordPress for some examples.

Why I Can’t Find .htaccess File?

There are two common reasons for not finding the .htaccess file in your website’s root folder. It’s either hidden by your file manager software, or it doesn’t exist at all.

We will explain both of them with solutions.

1. Your FTP Client is Not Showing Hidden Files

The dot before the htaccess file name indicates that it is a hidden file. By default, when you connect to your WordPress hosting server using an FTP client, it will not show the hidden files.

To make hidden files visible, you will need to change your FTP client settings.

For example, in FileZilla, you can find the option under ‘Server » Force showing hidden files’ menu.

If you are using the File Manager app in cPanel, then you will find the option to show hidden files before launching the app.

For other FTP clients, you will find the option to show hidden files in app settings or preferences menu.

After enabling this option, you would be able to view all hidden files including .htaccess file for your WordPress site.

2. The .htaccess File Doesn’t Exist

The second most common reason for missing .htaccess file is that your WordPress site has not generated it yet.

WordPress automatically generates .htaccess file because it is required to properly redirect permalinks.

If your .htaccess file is missing, then the first thing you need to do is to visit Settings » Permalinks page and click on ‘Save Changes’ button without changing anything.

WordPress will now try to generate the .htaccess file for you.

On some rare occasion, WordPress may not be able to generate the .htaccess file due to file permissions issue.

In that case, it will show you a message at the bottom of the Settings » Permalinks page, saying that the ‘.htaccess file is not writeable’.

You will need need to manually create the .htaccess file and add the required code inside it.

Simply copy and paste this code in a text editor like Notepad. After that, you need to save it as .htaccess file on your desktop.

Now connect to your website using an FTP client and upload the .htaccess file from your desktop.

If you get an error while uploading the file, then you need to change the file permission for your root directory.

Let’s suppose all your WordPress files reside under /home/johnsmith/public_html/ directory.

This makes public_html folder your root directory. You need to go to its parent directory and right click on the public_html folder. Select File Permissions, which will open a file permissions dialog box.

Now enter 755 into the file permission dialog box and then try to upload your .htaccess file to the public_html folder.

We hope this article helped you find .htaccess file on your WordPress site. You may also want to see our WordPress troubleshooting guide to learn how to diagnose and fix WordPress issues all by yourself.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post Why You Can’t Find .htaccess File on Your WordPress Site appeared first on WPBeginner.

from WPBeginner https://www.wpbeginner.com/beginners-guide/why-you-cant-find-htaccess-file-on-your-wordpress-site/

[siliconwebx]

How to Get Rid of /wordpress/ From your WordPress Site URL

Are you trying to remove /wordpress/ from your website’s URL? Sometimes beginners end up installing WordPress in a subdirectory, which causes /wordpress/ to appear in their website URL.

If you accidentally installed WordPress in a subdirectory and want to move it to the root directory, then you’re in the right place. In this article, we will show you how to get rid of /wordpress/ from your WordPress site’s URL.

Note: The method shown in this tutorial works for other subdirectories as well.

Why You See /wordpress/ in Your WordPress Site URL

WordPress is quite easy to install and nowadays most WordPress hosting companies offer quick WordPress installers in thier hosting control panel.

However, some beginners who are manually installing WordPress may end up accidentally installing it in a subdirectory. Most often this subdirectory is named wordpress.

This happens primarily because users end up uploading the wordpress folder they find inside the official WordPress.org download.

Let’s take a look at how to easily fix this and get rid of /wordpress/ from your site’s URL.

Removing /wordpress/ from WordPress Site URL

If you have just installed WordPress and there is no content on your website, then you can just go ahead and start over.

Simply delete the current installation, and follow the instructions in our WordPress installation tutorial to properly reinstall WordPress.

If you have already added content to your website, then there are two easy ways to remove the /wordpress/ from your site’s URL.

Method 1: Change WordPress Site Address

If you have an established WordPress site, then this method is easier and quicker. The downside of this method is that your media files such as images will still use /wordpress/ in the URL.

First, you need to login to your WordPress site’s admin area and go to Settings » General page.

You will notice the ‘WordPress Address’ and ‘Site Address’ fields and both will have the same URL.

You need to change the Site Address option and point to your root domain, e.g. http://bit.ly/2Fh70Wx and leave WordPress Address option as it is.

Once you do that, click on Save Changes button to store your settings.

Next, you need to connect to your website using an FTP client. Once you are connected, go to the /wordpress/ directory and download the .htaccess and index.php files to your computer.

If you are unable to locate the .htaccess file, then you may need to force your FTP client to show hidden files. If you are using Filezilla, then you need to click on Server from the menu bar and select ‘Force Showing Hidden Files’ option.

Once you have downloaded both files to your Desktop, you need to open index.php file in a text editor like Notepad. In this file you will find a line like this:

require( dirname( __FILE__ ) . '/wp-blog-header.php' );

This line loads the wp-blog-header.php file which is required to load your WordPress site.

What you need to do now is enter the correct location of the file by replacing the existing line with this one:

require( dirname( __FILE__ ) . '/wordpress/wp-blog-header.php' );

Save your changes and upload both index.php and .htaccess files from your desktop to the root of your domain using FTP. The root folder is the parent folder with the wordpress folder inside it usually called /www/ or /public_html/

That’s all. You can now visit your website using the root domain, and everything will work fine. However, if you need to login to your WordPress admin, then you will still need to go to the wp-admin inside the wordpress directory like this:

http://bit.ly/2HBBEtM

Method 2: Move WordPress to Root Directory

This method is more comprehensive and will permanently move your WordPress site from the subdirectory to the root folder of your website.

Step 1. Create a Duplicator Package

First, you need to install and activate the Duplicator plugin on your website. For more details, see our step by step guide on how to install a WordPress plugin.

Upon activation, you need to visit Duplicator » Settings page and click on the ‘Create New’ button.

This will launch the Duplicator wizard, which will create an installer package of your complete website. Click on the next button to continue.

Next, the plugin will run some scans. If everything looks OK, then you can click on the Build button.

Duplicator will now create a package and prompt you to download it along with the installer script. Go ahead and download both files to your computer.

Step 2. Create a New Database for a Fresh WordPress Install

You can use the existing WordPress database, but it is better to create a new one so that your old database is safe and unchanged. This way you could revert back to your site without much fuss if something goes wrong.

Visit your hosting account’s cPanel dashboard, scroll down to the ‘Databases’ section, and then click on the ‘MySQL Databases’ icon.

After that simply provide a name for your database and click on the ‘Create Database’ button.

Cpanel will now create a new database for you. After that, you need to scroll down to the ‘MySQL Users’ section.

From here you need to provide a username and password for your new database user and click on the ‘Create a user’ button.

Now you need to assign database permissions to the new user.

Scroll down to the ‘Add User to Database’ section. Simply select the database user you created from the dropdown menu next to the ‘User’ field, then select the database, and click on the add button.

Your new database is now ready to be used for the fresh WordPress installation.

Step 3. Run the Duplicator Wizard

Now, you need to upload the Duplicator archive package and the installer file you downloaded earlier to the root directory of your website.

This will be the directory containing the /wordpress/ folder.

After you have uploaded both files, open the installer script in a browser window. You will need to enter your site’s root URL and then prefix it with /installer.php.

http://bit.ly/2HymHd5

This will open the Duplicator installer wizard.

Check the terms and conditions box and then click on the ‘Next’ button to continue.

Next, it will ask you to provide the database information. Enter the information for the database we created earlier in step 2.

After entering database information, click on the next button to continue.

Duplicator will now unpack your WordPress database backup from the archive into your new database.

Next, it will ask you to update the site URL and Path. You don’t need to do anything here as it will automatically detect new URL and path. However, if it doesn’t, then you can manually enter it here.

Duplicator will now finish the migration, and you will be able to click on the Admin login button to access your website on the new location.

Step 4. Set up Subdirectory to Root Folder Redirects

Congrats, you have moved your WordPress site from subdirectory to the root folder.

Now it is time to setup redirects, so that your users and search engines can find your website’s new location.

First, you need to connect to your WordPress site using an FTP client and then delete the old /wordpress/ folder.

After that, switch to the admin area of your WordPress site. Since you have moved it to the root of your website your WordPress admin URL will be like this:

http://bit.ly/2HKXzz5

Now, you need to install and activate the Redirection plugin. For more details, see our step by step guide on how to install a WordPress plugin.

Upon activation, you need to visit Tools » Redirection page. The plugin will now show you a setup wizard. Simply click on the continue setup and then finish setup button.

Next, you need to switch to the ‘Redirects��� tab and add your new redirect.

First check the ‘Regex’ checkbox at the corner of the first field.

After that, For source URL you will add https://example.com/wordpress/.* and for Target URL you will add https://example.com/$1.

Don’t forget to replace example.com with your own domain name. Click on the ‘Add Redirect’ button to save your changes.

From now on all users accessing your website with /wordpress/ in the URL will be automatically redirected to correct posts with your new root URL.

That’s all. We hope this article helped you learn how to get rid of /wordpress/ from your WordPress site URL. You may also want to see our comprehensive guide to most common WordPress errors and how to fix them.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Get Rid of /wordpress/ From your WordPress Site URL appeared first on WPBeginner.

😉SiliconWebX | 🌐WPBeginner

[sheilalmartinia]

How to Get Rid of /wordpress/ From your WordPress Site URL

Are you trying to remove /wordpress/ from your website’s URL? Sometimes beginners end up installing WordPress in a subdirectory, which causes /wordpress/ to appear in their website URL.

If you accidentally installed WordPress in a subdirectory and want to move it to the root directory, then you’re in the right place. In this article, we will show you how to get rid of /wordpress/ from your WordPress site’s URL.

Note: The method shown in this tutorial works for other subdirectories as well.

Why You See /wordpress/ in Your WordPress Site URL

WordPress is quite easy to install and nowadays most WordPress hosting companies offer quick WordPress installers in thier hosting control panel.

However, some beginners who are manually installing WordPress may end up accidentally installing it in a subdirectory. Most often this subdirectory is named wordpress.

This happens primarily because users end up uploading the wordpress folder they find inside the official WordPress.org download.

Let’s take a look at how to easily fix this and get rid of /wordpress/ from your site’s URL.

Removing /wordpress/ from WordPress Site URL

If you have just installed WordPress and there is no content on your website, then you can just go ahead and start over.

Simply delete the current installation, and follow the instructions in our WordPress installation tutorial to properly reinstall WordPress.

If you have already added content to your website, then there are two easy ways to remove the /wordpress/ from your site’s URL.

Method 1: Change WordPress Site Address

If you have an established WordPress site, then this method is easier and quicker. The downside of this method is that your media files such as images will still use /wordpress/ in the URL.

First, you need to login to your WordPress site’s admin area and go to Settings » General page.

You will notice the ‘WordPress Address’ and ‘Site Address’ fields and both will have the same URL.

You need to change the Site Address option and point to your root domain, e.g. http://www.example.com and leave WordPress Address option as it is.

Once you do that, click on Save Changes button to store your settings.

Next, you need to connect to your website using an FTP client. Once you are connected, go to the /wordpress/ directory and download the .htaccess and index.php files to your computer.

If you are unable to locate the .htaccess file, then you may need to force your FTP client to show hidden files. If you are using Filezilla, then you need to click on Server from the menu bar and select ‘Force Showing Hidden Files’ option.

Once you have downloaded both files to your Desktop, you need to open index.php file in a text editor like Notepad. In this file you will find a line like this:

require( dirname( __FILE__ ) . '/wp-blog-header.php' );

This line loads the wp-blog-header.php file which is required to load your WordPress site.

What you need to do now is enter the correct location of the file by replacing the existing line with this one:

require( dirname( __FILE__ ) . '/wordpress/wp-blog-header.php' );

Save your changes and upload both index.php and .htaccess files from your desktop to the root of your domain using FTP. The root folder is the parent folder with the wordpress folder inside it usually called /www/ or /public_html/

That’s all. You can now visit your website using the root domain, and everything will work fine. However, if you need to login to your WordPress admin, then you will still need to go to the wp-admin inside the wordpress directory like this:

http://www.example.com/wordpress/wp-admin

Method 2: Move WordPress to Root Directory

This method is more comprehensive and will permanently move your WordPress site from the subdirectory to the root folder of your website.

Step 1. Create a Duplicator Package

First, you need to install and activate the Duplicator plugin on your website. For more details, see our step by step guide on how to install a WordPress plugin.

Upon activation, you need to visit Duplicator » Settings page and click on the ‘Create New’ button.

This will launch the Duplicator wizard, which will create an installer package of your complete website. Click on the next button to continue.

Next, the plugin will run some scans. If everything looks OK, then you can click on the Build button.

Duplicator will now create a package and prompt you to download it along with the installer script. Go ahead and download both files to your computer.

Step 2. Create a New Database for a Fresh WordPress Install

You can use the existing WordPress database, but it is better to create a new one so that your old database is safe and unchanged. This way you could revert back to your site without much fuss if something goes wrong.

Visit your hosting account’s cPanel dashboard, scroll down to the ‘Databases’ section, and then click on the ‘MySQL Databases’ icon.

After that simply provide a name for your database and click on the ‘Create Database’ button.

Cpanel will now create a new database for you. After that, you need to scroll down to the ‘MySQL Users’ section.

From here you need to provide a username and password for your new database user and click on the ‘Create a user’ button.

Now you need to assign database permissions to the new user.

Scroll down to the ‘Add User to Database’ section. Simply select the database user you created from the dropdown menu next to the ‘User’ field, then select the database, and click on the add button.

Your new database is now ready to be used for the fresh WordPress installation.

Step 3. Run the Duplicator Wizard

Now, you need to upload the Duplicator archive package and the installer file you downloaded earlier to the root directory of your website.

This will be the directory containing the /wordpress/ folder.

After you have uploaded both files, open the installer script in a browser window. You will need to enter your site’s root URL and then prefix it with /installer.php.

https://example.com/installer.php

This will open the Duplicator installer wizard.

Check the terms and conditions box and then click on the ‘Next’ button to continue.

Next, it will ask you to provide the database information. Enter the information for the database we created earlier in step 2.

After entering database information, click on the next button to continue.

Duplicator will now unpack your WordPress database backup from the archive into your new database.

Next, it will ask you to update the site URL and Path. You don’t need to do anything here as it will automatically detect new URL and path. However, if it doesn’t, then you can manually enter it here.

Duplicator will now finish the migration, and you will be able to click on the Admin login button to access your website on the new location.

Step 4. Set up Subdirectory to Root Folder Redirects

Congrats, you have moved your WordPress site from subdirectory to the root folder.

Now it is time to setup redirects, so that your users and search engines can find your website’s new location.

First, you need to connect to your WordPress site using an FTP client and then delete the old /wordpress/ folder.

After that, switch to the admin area of your WordPress site. Since you have moved it to the root of your website your WordPress admin URL will be like this:

https://example.com/wp-admin

Now, you need to install and activate the Redirection plugin. For more details, see our step by step guide on how to install a WordPress plugin.

Upon activation, you need to visit Tools » Redirection page. The plugin will now show you a setup wizard. Simply click on the continue setup and then finish setup button.

Next, you need to switch to the ‘Redirects’ tab and add your new redirect.

First check the ‘Regex’ checkbox at the corner of the first field.

After that, For source URL you will add https://example.com/wordpress/.* and for Target URL you will add https://example.com/$1.

Don’t forget to replace example.com with your own domain name. Click on the ‘Add Redirect’ button to save your changes.

From now on all users accessing your website with /wordpress/ in the URL will be automatically redirected to correct posts with your new root URL.

That’s all. We hope this article helped you learn how to get rid of /wordpress/ from your WordPress site URL. You may also want to see our comprehensive guide to most common WordPress errors and how to fix them.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Get Rid of /wordpress/ From your WordPress Site URL appeared first on WPBeginner.

from WPBeginner https://www.wpbeginner.com/wp-tutorials/how-to-get-rid-of-wordpress-from-your-wordpress-site-url/

[siliconwebx]

What’s an “inode” and How Does It Affect My WordPress Website?

One of the most common (and misunderstood) elements of a website and web hosting is the inode. If you run your own website or handle maintenance on any level at all, you will deal with inodes at some point. Whether that is through routine maintenance or attempting to fix an error, knowing what an inode is and how it affects your WordPress installation is imperative to your long-term success.

What is an Inode?

In a very general sense, an inode is a single file within your file system. For most users, that’s enough information to deal with almost everything that they will come across.

More technically, however, an inode is where the metadata for files is stored on UNIX systems (Linux servers and Apple computers are UNIX based). Inodes are the table entries that are linked to by directories and files Inodes contain all sorts of information:

This metadata includes (1) the size of the file (in bytes) and its physical location (i.e., the addresses of the blocks of storage containing the file’s data on a HDD), (2) the file’s owner and group, (3) the file’s access permissions (i.e., which users are permitted to read, write and/or execute the file), (4) timestamps telling when the inode was created, last modified and last accessed and (5) a reference count telling how many hard links point to the inode.

Because most web servers are Linux-based, inode management is going to be important. You can think of them like they are links to your website. You can have multiple links pointing to the same page of your site, but that doesn’t mean there are multiple copies of that page. The same is true of files and inodes.

While technically, there is not a 1:1 relationship, you will find many instances where there is only 1 file linked to 1 inode. Most users can work under the idea they are.

The Problem with Inodes

They run out. They are finite. And you probably aren’t tracking your inode usage.

Not too long ago, I received the “Warning: Account YourSite.com Reached 80% Of The Allowed Inode Quota” email from Siteground out of the blue. I hadn’t done anything out of the ordinary, but somehow, I was stacking up my inodes like a tower. I would guess that if you’re running multiple installations of WordPress on your hosting account, you have gotten (or will get) a similar email.

Now, in the email, they’re very straightforward: To decrease the number of inodes, you need to reduce the number of files and folders on your account via cPanel – File Manager or your preferred FTP client. And in essence, that’s all you have to do. But it’s a bit more complicated than that because if you’ve had your host for any amount of time, you’ve probably got a pretty decent archive of files and folders in there.

To check your inode usage, you will want to log into your cPanel and look for the Stats box. In most versions of cPanel, it will be to the left of the page somewhere. You will see primarily the Disk Usage Space in MB and GB, as well as the number of inodes you’re allowed and the number of inodes you’re using at that moment.

Luckily, like most things about WordPress, the CMS is put together in a way that makes managing your inodes relatively straightforward.

Why Inodes Matter for WordPress Users

Many of you may never have to work with inodes. In day-to-day business, you won’t really notice them at all. As long as everything is going well with your site, nothing should make you ever even see the word. It’s when something goes wrong that you will start seeing errors in your WordPress dashboard or somewhere else.

Generally, every hosting provider out there who uses cPanel (which is most of them, unless you’re going for managed hosting) has allotted you a certain number of inodes based on your package. The rule is generally the more you pay, the more inodes you get.

Keep in mind that this is entirely separate from how much storage space you have. The two may be 1:1-ish in volume, but you will generally run out of inodes before you run out of storage space because inodes are a lot smaller in terms of bits and bytes than most of your files (because they’re only part of the file itself).

That said, WordPress users often find themselves fighting some inode-centric issues.

How WordPress Users Build Up Inodes

While every CMS out there has its own unique ways of taking up inodes, WordPress has some that are specific to its ecosystem. Primarily images, plugins, and themes. Let’s dig in and find out why and what we can do about it.

Images

Images in your media library likely take up a ton of your inodes. Even if you don’t have thousands and thousands of them. I would wager that most of you upload images to your site. And in theory, 1 image equals 1 inode. But that’s not how things actually work. Depending on your theme and your image compression plugin, that 1 image can take nearly a dozen inodes. How? By keeping renders of multiple sizes in storage.

If you check the details of any image in your library and see a file size, then it’s an inode. Think about that for each and every image in your media library. For this one particular site, I have 562 items in the media library. Assuming (probably incorrectly) that they each have 11 versions, that’s 6,000+ inodes. Literally eleven times what it should be.

And that’s for one site. If you take into account the number of sites on any general hosting plan, that number can really add up. On my own account, I have a dozen installations of WordPress running. On top of the Core files from each install, the media libraries from all the users increase inode usage.

Plugins and Themes

You have a few reasons that plugins and themes take up so many inodes. The first is simply that many people have tons of them installed, even if they’re deactivated.

And within each of these plugin folders, dozens and dozens of files are taking up inodes. Some plugins are obviously lighter than others, but all of them add bulk to your installation. So remember that it’s generally best practice to delete any plugins that you aren’t currently using.

Themes work the exact same way. There’s no telling how many themes you have installed on your WordPress site if you’ve had it for a decent amount of time. Even if those themes are simply the default WordPress themes, you have a lot of inodes being used. If you’re not using a theme, delete it. If you’ve made customizations via a child theme, however, it’s generally okay to keep it there (or make a backup) since you can’t just reinstall it as easily as you can the parent theme.

Caching Plugins and Backup Utilities

Comet Cache. WPRocket. Updraft. iThemes. WordFence. WP Super Cache. W3 Total Cache. Sucuri.

All of these (and more) take up precious inodes. For the most part, that’s okay. They’re amazing plugins that make your life easier and your users’ experiences on your site better. But left unchecked, however, the cache files and backup files and security reports can build up.

So every once in a while, make sure that you clear the cache on your site and let it repopulate itself. Most of the time, you can find a Purge Cache or Delete Cache button in the admin toolbar.

Additionally, extra backups from plugins like UpdraftPlus can take up precious space. So check to see what you have stored on your local server. You can do this from within your WP admin panel for most backup utilities. Or you can check via FTP.

On top of these backups taking up inodes and storage space on your server, they’re also vulnerable to hackers who may get into your installation. So keeping them in a remote destination (Dropbox or Google Drive, for example) is going to be the best idea.

How to Fix Common Inode Errors

And even though WordPress has platform-specific inode issues, there are some that are common across the web. Whether you’re on Drupal,  Joomla, WordPress, or even Ghost, you may have to fix these at some point.

Emails won’t send, either through a traditional client, via autoresponders, or from forms on the site itself

Can’t receive emails

Uploads consistently fail

Posts and Pages won’t update or even create

Users cannot access the site

In some cases, migration from one host to another might be blocked

In all of these cases, what might be the culprit is that the server is approaching the top end of its inode quota. Or that it’s completely out of inodes. Remember, even if you’re using only a portion of your storage capacity, you can still use up your inodes.

Every time an email is sent or received, a file is generated. If there are no inodes, no file can be made. If your inodes are full, uploads will fail because there is simply nowhere to store the data. The same can be said for posts and pages in WordPress or other CMS platforms can’t generate the necessary files without a spot. Even when users visit the page, files are generated — cookies, tokens, cached files. If there’s no inode, those users get nothing served to them.

When migrating from one host to another, your inode allotment may be different. Mine was the last time I swapped, personally. So you may not even be near your current quota, be already be over your upcoming one. It may sound like a pain, but it was really easy to fix, actually.

Here are the best ways to remove files and free up some space to fix these common inode errors.

Delete Old Emails

You see, every time an email is sent or received, it creates a file on your server (assuming that you’re not using an external mail service). That means all your mail is taking up inodes. If you archive or simply hold your emails in your inbox, those are sitting on your server, stagnating. So it’s time to delete them. You can do this in your normal client, or you can do it via FTP or through your cPanel’s File Manager.

Simply go into the root directory of your site and find the Mail folder. Under it will be directories for each domain you have an email address for, and under each of those will be any of the aliases you’ve set up. Each one of those folders is important and can be full of inode-stealing files. You will be primarily concerned with the cur and new directories, though. Sometimes Junk.

After just deleting the new emails in this one address, I went from 218316 inodes used to 218218. You should have an even greater gain because this email address was very rarely used in the first place. Just remember to back up all the emails before you delete them. You can’t get them back otherwise.

Clear Your Temp Folders

Temporary files are fantastic beasts. If you know where to find them, you can make sure that they are doing their jobs, but not taking up far too many resources. Whenever you see a tmp directory, this is where those temporary files are stored. Session tokens, cache files, traffic logs, all sorts of stuff that are great at the time, but serve no purpose later.

Unless you’ve set up an automation or CRON job to clear out temporary files, you may need to go in every once in a while and perform a little housekeeping. Primarily these will be in your root directory under tmp.

As a general rule of thumb, you can delete any log files, cache files, or session files. For the most part, you will see them noted very clearly. Usually the file name will contain sess or cache or log, making your job very easy.

Most of the files you delete will be server logs and traffic logs. As long as you have a backup of these files, go through your tmp folders and delete what you need to. In this particular example, I am clearing out the webalizer, webalizerftp, horde, awstats, and analog directories. Please keep in mind that removing these files will remove server statistics and logs, so back them up first if necessary.

You can check the dates on them, too. Depending on your site, you may not need logs all the way back to 2011.

Additionally, you will find a handful of files in your primary tmp folder, too. They might be a mix of session files, log files, and other files that you’re not sure about. Just like everything with computers and web development, if you don’t know what it is, leave it alone. But it is very important that you do not delete any files that have a .sock extension. And to a lesser extent, .lock.

Clear Your Log Files

Similar to the tmp folder, the logs folder is a root directory that contains archive upon archive of your server’s logs. Your server begins keeping a log for each domain for each month you’ve had it active on your host. That can be a lot of logs. Make a backup of them because they’re kind of important and delete away.

Delete Unnecessary Website Installations

There are two reasons that you don’t want to have superfluous installations taking up your inodes. The first is, well, you’re wasting inodes on something that you’re not using. The second is that forgotten websites are vulnerable to major security threats and are the most common way for hackers to get into shared servers via brute force attacks.

Remember how I said earlier there were 12 installations of WP on my personal hosting plan? Well, 8 of those 12 are completely (or at least mostly) useless. Of those, 6 can be deleted without worry and 2 are placeholders.

There are over 5,000 files in each WordPress installation — which is at least 5,000 inodes — and if you did anything to customize it or add plugins or themes…well, you and I should both probably take a look at what we have sitting around on our server.

Wrapping Up

Running out of inodes on your host is annoying and disruptive. Even if you get warned long before you reach capacity, you still have to take a good amount of time to clear out data from your server. However, if you take a quick pass through all of the tips above, you should be able to easily lower inode usage by at least 20% in one pass.

Whether you’re on WordPress or some other CMS, inode usage is something that may not come up very often, but when it does, you’ll be very glad that you’re ready for it.

What have you found is the best way to lower inode usage on your sites?

Article featured image by strangebirdy / shutterstock.com

The post What’s an “inode” and How Does It Affect My WordPress Website? appeared first on Elegant Themes Blog.

😉SiliconWebX | 🌐ElegantThemes

[sheilalmartinia]

How to Install WordPress in a Subdirectory (Step by Step)

Do you want to install WordPress in a subdirectory? Installing WordPress in a subdirectory allows you to run multiple WordPress instances under the same domain or even a subdomain name. In this article, we will show you how to install WordPress in a subdirectory without affecting the parent domain name.

Subdomain vs Subdirectory? Which One is Better for SEO?

Normally, you would want to start a WordPress website on its own domain name (for example, wpbeginner.com). However, sometimes you may want to create additional websites on the same domain name.

This can be done by either installing WordPress in a subdomain (http://newebsite.example.com) or as a subdirectory (http://example.com/newwebsite/).

One question that we get asked is which one is better for SEO?

Search engines treat subdomains differently from root domain names and assign them rankings as a totally different website.

On the other hand, sub-directories benefit from the domain authority of the root domain thus ranking higher in most cases.

An easier way to create separate WordPress sites in both subdomain or subdirectory is by installing WordPress multisite network.

However, if you want to keep two websites managed separately, then you can install different instances of WordPress.

That being said, let’s take a look at how to install WordPress in a subdirectory.

Step 1. Create a Subdirectory under The Root Domain Name

First you need to create a subdirectory or folder under your root domain name. This is where you will install WordPress files.

Connect to your WordPress hosting account using a FTP client or File Manager in cPanel.

Once connected, go to the root folder of your website. Usually it is the /public_html/ folder. If you already have WordPress installed in the root folder, then you will see your WordPress files and folders there.

Next, you need to right click and select ‘Create new directory’ from the menu.

You need to be careful when choosing the name for your subdirectory. This will be part of your new WordPress site’s URL and what your users will type in their browsers to reach this website.

For example, if you name this directory travel-guides then your WordPress website’s address will be:

http://example.com/travel-guides/

Step 2. Upload WordPress Files

Your newly created subdirectory is empty at the moment. Let’s change that by uploading WordPress files.

First you need to visit WordPress.org website and click on the download button.

Your browser will now download the zip file containing the latest WordPress software to your computer.

After downloading the file, you need to select and extract it. Mac users can double click the file to extract it and Windows users need to right click and then select ‘Extract All’.

After extracting the zip file, you will see ‘wordpress’ folder containing all the WordPress files.

Now let’s upload these files to your new subdirectory.

Connect to your website using a FTP client and go to the subdirectory you created in the first step.

In the local files panel of your FTP client, go to to the WordPress folder you just extracted.

Select all files in the WordPress folder and then upload them to your new subdirectory.

Step 3. Create New Database

WordPress stores all your content in a database. You need to create a new database to use with your new WordPress site installed in a subdirectory.

First, you need to login to the cPanel dashboard of your WordPress hosting account. Click on ‘MySQL Databases’ under the databases section.

On the next screen, you need to provide a name for your new database and then click on ‘Create Database’ button to continue.

Your cPanel dashboard will now create the new MySQL database. In order to use this database you need to create a MySQL username.

Scroll down to MySQL Users section and provide a new username and password. Click on ‘Create User’ button to continue.

Next, you need to give this newly created user privileges to work on the database you created earlier.

Scroll down to ‘Add user to database’ section. Select your MySQL username and then select your newly created database.

Click on Add button to continue.

Cpanel will now grant the MySQL user full privileges on your newly created database.

Step 4. Install WordPress

Now that everything is in place, you can go ahead and install WordPress. Simply visit the directory you created earlier in a web browser by typing the URL like this:

http://example.com/your-subdirectory-name/

This will bring up the WordPress installation wizard. First you need to select the language for your WordPress website and click on the continue button.

Next, you will be asked to provide your WordPress database name, database username, password, and host. Enter the database details and click on the submit button.

WordPress will now connect to your database and you will see a success message like this:

Click on ‘Run the install’ button to continue.

On the next screen, you will be asked to provide a title for your website and choose an admin username, password, and email address.

After entering your website details, click on ‘Run install’ button to continue.

WordPress will now set up your website and will show you a success message:

You can now go ahead and login to your new WordPress website installed in the subdirectory.

Step 5. Fix Permalinks

If you have a separate WordPress install in the root directory, then the .htaccess files of your subdirectory will cause conflict. This will result in 404 errors on your website.

To solve this, you need to edit the .htaccess file in your subdirectory WordPress install. Replace the code inside your .htaccess file with the following code:

# BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase /your-subdirectory/ RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /your-subdirectory/index.php [L] </IfModule> # END WordPress

Don’t forget to replace /your-subdirectory/ with your own subdirectory name.

We hope this article helped you install WordPress in a subdirectory. You may also want to see our ultimate step by step WordPress SEO guide for beginners.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Install WordPress in a Subdirectory (Step by Step) appeared first on WPBeginner.

from WPBeginner http://www.wpbeginner.com/wp-tutorials/how-to-install-wordpress-in-a-subdirectory-step-by-step/