http://www.kriesi.at/support/topic/broken-links-webkitgecko-after-upgrade-to-wp-351-post-entry-css-class Support Forum - Topic: Broken links (Webkit/Gecko) after upgrade to WP 3.5.1. post-entry CSS class? en-US Fri, 24 May 2013 22:59:33 +0000 http://bbpress.org/?v=1.0.2 q http://www.kriesi.at/support/search.php http://www.kriesi.at/support/topic/broken-links-webkitgecko-after-upgrade-to-wp-351-post-entry-css-class#post-97570 Wed, 20 Feb 2013 05:16:01 +0000 Ismael 97570@http://www.kriesi.at/support/ <p>Hi anibalrojas,</p> <p>Is the Mission/Vision page the only page in your site that has unclickable links? If it's the only one, then kindly add this css code on your Quick CSS or at the bottom of custom.css:</p> <pre><code>.page-id-956 .post-entry { float: none; }</code></pre> <p>or<br /> <pre><code>.page-id-956 .post-entry { float: none !important; }</code></pre> <p>Regards,<br /> Ismael </p> http://www.kriesi.at/support/topic/broken-links-webkitgecko-after-upgrade-to-wp-351-post-entry-css-class#post-97539 Tue, 19 Feb 2013 23:04:35 +0000 anibalrojas 97539@http://www.kriesi.at/support/ <p>Thanks for asking.</p> <p>In this page the links aren't clickable:</p> <p><a href="http://cenaif.com/vision-mision-valores/" rel="nofollow">http://cenaif.com/vision-mision-valores/</a></p> <p>In this they are clickable:</p> <p><a href="http://cenaif.com/" rel="nofollow">http://cenaif.com/</a> </p> http://www.kriesi.at/support/topic/broken-links-webkitgecko-after-upgrade-to-wp-351-post-entry-css-class#post-97106 Sun, 17 Feb 2013 08:06:40 +0000 Dude 97106@http://www.kriesi.at/support/ <p>Hey! </p> <p> Please post a link to your website. </p> <p> Regards,<br /> Peter </p> http://www.kriesi.at/support/topic/broken-links-webkitgecko-after-upgrade-to-wp-351-post-entry-css-class#post-97083 Sat, 16 Feb 2013 22:41:27 +0000 anibalrojas 97083@http://www.kriesi.at/support/ <p>After updating to WordPress 3.5.1 most of the links in the site stopped working (are not clickable) </p> <p>The cursor doesn't change on hover and looks like no click event is being triggered also. Actually Firebug and the Chrome inspector behave funky.</p> <p>I tracked down the problem to the post-entry CSS class, any container including this class will produce this behavior in the included anchors.</p> <p>I suppose there is some JS interfering, but I haven't been unable to track it down.</p> <p>I shutted down almost all plugins without luck also. </p>