While trying to update the WP LinkedIn widget on a WordPress blog, I ran into an HTTP error I had never seen before: 414.
HTTP error 414 indicates that the URI is too long for the web server to interpret it.
In the case of a WordPress blog, this is likely caused by a security feature of the iThemes security plugin. If iThemes is being used, the first step would be to turn off the “Filter Long URL Strings” checkbox. This can be accessed through the WordPress admin console: Security –> Settings –> System Tweaks.
The checkbox is about halfway down the page.
I would suggest turning this off only long enough to complete whatever administrative action you are doing, and then turning it back on, so as not to create an unnecessary vulnerability.
The method described in that post worked fine until Thesis 2.4 was released last August. At that time, I noticed that my columns were no longer the full width of the window, and did not change size as I expanded or shrank the window. I sent an email to Thesis support and was told that a Box called Fix CSS would likely fix my problem. I installed it, but to no avail. Upgrading to Thesis 2.6 last month also had no effect.
Last week I decided to send another email and got a little more information. The creator of Thesis responded. Part of the message is below.
“Thesis 2.6 has ‘clarified’ the way you can use variables. Here’s how it works…
Modify the Skin CSS, Editor CSS, or CSS Variables that come with your Thesis Skin. Whenever a Skin is updated, these three items will be overwritten, and you will lose any changes you’ve made to them.
Isolate ALL your CSS changes to the Custom CSS interface. Your modifications will be safe here during future Skin updates.
Create inline variables inside your Custom CSS interface, as seen in the image below:
You can REFERENCE existing CSS Variables in your Custom CSS code, and you can also create and reference your own variables (like those shown in the image above) here as well.”
Now I had to implement the same steps as before in the previous post, but using this new method.
While the changes causing the builtin variables to revert to their original values may have been implemented in 2.6, my code had quit working at 2.4. So there’s a mystery! First, I removed the custom code and deleted the new variables from the Skin CSS so that it would be as it would directly downloaded the Thesis website.
Then, I basically set up new variables in the Custom CSS using the syntax shown in the screenshot above. I hit a snag here, however. For whatever reason, the CSS engine no longer supported the CSS calc() function! Also, I discovered that some of the CSS class names I originally used seemed not to affect the style of the column any longer.
The code below, which I appended to the bottom of my Custom CSS, does several things. First, it declares variables for the Custom CSS page in Thesis. Secondly, it implements those custom variables on the appropriate CSS classes and overrides the Skin CSS in all places where the variables $w_total and $w_content were used. Lastly, it declares a CSS variable to store the value in the builtin $w_sidebar Thesis variable. This will be useful in the next step, in which I will use a workaround for the lack of a working CSS calc() function.