In this article I will cover how to enable SVG uploads on your WordPress website quickly and easily using a free WordPress plugin.
As of this writing, SVG uploads are not permitted by the WordPress core for security (and for good reason). SVG files are basically XML files, which may include malicious code opening your WordPress website to attack. These include but may not be limited to XML external entity attacks (XXE), bomb nested entities (BNE) and Cross Site Scripting (XSS) attacks.
I recently completed and uploaded a client’s web site to their server. Upon doing so the WordPress website generated an Internal Server Error 500. Checking the .htaccess file and other server settings everything checked out. Looking into their servers error log I discovered a soft error relating to file and folder permissions.
Sure enough, the uploaded project had all sorts of incorrect permissions set. I believe this was caused by an issue with the compression program I was using to archive the project into one file forĀ easier uploading to their server.
Making sure your WordPress installations’ file and folder permissions are set correctly is critical to keeping your WordPress site safe. Not only for security, but if the file and folder permissions are incorrect, you’ll run across any number of issues importing media, creating posts and so on.
There is no “push button” fix for this issue. However, the following solution is simple enough without the use of any plugins and only requires about 5 minutes of attention. You will want to use an FTP client (such as FileZilla) for this. It should also go without saying that you need to have a recent full backup of your website, just in case you push the wrong button(s).
When you’re ready, fire up your FTP client and log onto your web server and follow the instructions below.
I was recently migrating a WordPress website from one server to another. Everything was setup correctly and had transferred over without issue, or so I thought.
When I attempted to view the website or access the WordPress backend login I was prompted to install WordPress, again.
In this article I review what might be causing the WordPress installation page to show up again even though WordPress is already installed and configured. It is assumed you have at least basic web hosting experience. If you are looking for a step by step instructional tutorial, you’ll have to try another Brave search result.
I frequently use Adobe Photoshop to enhance and compress my web related images. When using the “Save for Web & Devices” feature it automagically replaces any spaces, within the filename, with a dash for Unix compatibility purposes. This is not always necessary, so in this article I will show you how to disable the automatic replacement of spaces with dashes when using Save for Web in Photoshop.
Another negative result of this automatic insertion of dashes in place of spaces is when uploading images to WordPress. WordPress pulls the filename and inserts it into the Title field for the uploaded image. For search engine optimization purposes this is okay, but the dashes make it look unsightly when you hover your mouse over the image on the frontend. I then have to manually remove those dashes from the image title and save the changes. Turning the insertion of dashes feature off when using the Save for Web & Devices feature in Photoshop would prevent these additional steps. So lets get into doing so.
[ See the officially released version of this plugin on WordPress.org ]
Gravity Forms comes with a few built-in CSS classes, called CSS Ready Classes, for you to choose from when building your forms. However, unless you have memorized them you will have to look them up.
We’ve updated Brad’s (6+ year old) Gravity Forms CSS Ready Class Selector WordPress plugin which works as a handy CSS Ready Class reference tool. When editing your forms, selecting the old ellipsis image from the Custom CSS Class label within the Appearance tab, this plugin would generate a convenient popup containing all the latest available CSS Ready Classes. But as we mentioned, its over 6 years old and needed to be updated. It was missing a few CSS Ready Classes and had an invalid link to the Gravity Forms CSS Ready documentation. Plus, wouldn’t it be handy to know which fields the intended class would work with? Then we discovered Mike’s forked version and enhancements which further streamlined the code and removed the unnecessary accordions. We didn’t know that we didn’t want the accordions until they were gone.
Our revision of this convenient plugin further refined and streamlined the popup display.
This new plugin, as before, from within your forms’ fields, select the Appearance tab and click the new “CSS” link next to the Custom CSS Class field. This will open the handy reference popup. We replaced the old ellipsis image button with a simple link.
Browse through the various CSS Ready Classes and select the ones you want to have added to your field. Double click on your last selection to automatically close the popup or just hit esc. When you hover your cursor over any class, a description (via link title) will appear of the classes function and intended use. View this project on GitHub.
[ See the officially released version of this plugin on WordPress.org ]
When you first setup your WordPress website, the wp_mail() function (which handles sending email), defaults to “WordPress” as a email sender name and “wordpress@” for all outgoing emails.Ā For this reason, I have always made it a point to establish a “wordpress@” email address when setting up any client account to reduce email delivery issues.
But this is a pain and requires someone monitor the account or have messages forwarded to another one. It also doesn’t look very professional to receive such WordPress branded emails from what should be a trusted company brand.
You can use any number of contact form plugins to receive email messages from your web site. However, if it’s WordPress that is sending out a WordPress email, then the mailtoĀ function will default to: WordPress <wordpress@>.
Outgoing email notifications are important, and you should be using your own brand and web site email address. This increases the authenticity of your brand, product or service as well as name recognition among your visitors and subscribers. No doubt, to a subscriber, receiving an email from WordPress <wordpress@> looks very unprofessional. It may even result in email delivery issues due to Internet Service Providers and end user email spam filters.
Introducing WPFrom Email, a free WordPress Plugin aimed at helping you quickly and easily update the default WordPress sender FROM Name and Email Address.
[ See the officially released version of this plugin on WordPress.org ]
WP Imsizer (short for Image Resizer) is a plugin for WordPress which will save you and your clients or fellow blog contributors from having to manually resize all of your images to a more visitor friendly size. You can even restrict the total file size of uploaded images and even disable the WordPress image 2560px threshold limit which was introduced in version 5.3.
When someone uploads an image that is larger than your set dimensions, WP Imsizer will automatically scale it down to your desired pre-configured size and replace the original image.
The WP Imsizer Plugin is ideal for WordPress web sites and blogs that do not require super high resolution images. This will save space on your server, speed up your page speed performance, and reduce bandwidth utilization for both you and your visitors. As a result of being able to quickly display your media on your web site, this will most likely improve your search engine ranking.
If you already have WordPress installed but are being redirected to the WordPress installation page you may have an issue with your database or configuration file. In this article I will go over some potential solutions to help you restore access to your existing WordPress site.
In this article I will show you how to disable trackbacks and pingbacks on your old WordPress pages and posts quickly using a simply MySQL query.
Before doing so you will want to make sure that you have disabled link notifications (pingbacks and trackbacks) for any future posts or pages using the WordPress backend. Simply visit the “Settings > Discussion” admin page and uncheck the “Allow link notifications from other blogs (pingbacks and trackbacks) on new posts” option.
As stated, this particular setting only works going forward, on “new posts and pages“. Now to remove trackbacks and pingbacks on our old posts and pages.
Need to prevent a visitor or user from changing a specific form field on one of your Gravity Forms? Using the provided code snippet within this article, you can convert any input field into a “read-only” field. This type of field is different from a hidden field as it will display the contained data but prevent the visitor from altering it.
Sometimes making a field read-only can be useful, allowing you to then utilize that field for dynamic display of various messages. If you want to change a field to be read-only, you currently need to use JavaScript to do so. The following code snippets will help you accomplish this.
