You may receive the below error when attempting to upload files via the WordPress Add New Media page. The error is fairly specific regarding what the issue is however you may be unfamiliar with how to resolve the issue so below I will explain how to modify php.ini and resolve the error.
I have used the NextGen Gallery WordPress plugin on a bunch of different projects and have always been satisfied with the functionality. On a recent WordPress project I was working on I installed NextGen Gallery assuming I would use it however after I got a bit further on the project I decided it wasn’t necessary and that it would be easier to simply use the default WordPress media uploading capabilities along with the “Lightbox 2” and the “Flexible Upload D3Z Edition” WordPress plugins instead. While NextGen gallery has tons of functionality and typically is easy to use for this project there would be many authors and I needed the path of least resistance to allow authors to write articles.
I have had FORCE_SSL_ADMIN set for quite awhile now in my wp-config.php file which forces all traffic to /wp-admin/ to be HTTPS. When I initially configured this setting it broke numerous WordPress plugins which I fixed however I missed MM-Forms being broken. The issue was the exact same as previous plugins that had the issue so it wasn’t to hard to fix but I wanted to share in case anyone else is having trouble getting the MM-Forms plugin working over SSL. Below I will explain what lines need to be changed to get MM-Forms working over HTTPS including syntax, line numbers, and old code.
I had been using the default page templates on a development installation of WordPress which is a direct copy of another WordPress installation. During the process of editing some pages I decided I wanted to try a couple different types of page templates. The templates were exact copies of the default page view but with one line of code modified such as not displaying the title of a page.
I have been using the WP-Forum WordPress plugin for along time now and even though I am moving away from using it I do still think its a great plugin. There are two reasons I am getting away from it which include the fact that it does not validate using the W3C Markup Validation Service and the main reason is because we have launched Engage which will allow users an easier way to interact with Question Defense.