Jump to content
Sign in to follow this  
julianbalog

WP-Syntax plugin problem with iBlogPro

Recommended Posts

julianbalog

The WP-Syntax plugin won't show the horizontal scrollbar for code inserts within the default

 tags, if the code line exceeds the 'visible' area of the iBlogPro theme.

Share this post


Link to post
Share on other sites
Kate

Hi Julian, I'm sorry... I'm not sure I completely understand the question. But, it actually sounds like it might be a plugin issue. Do you notice the same issue when using, for instance, the default TwentyTen theme?

Share this post


Link to post
Share on other sites
julianbalog

I tried using different themes and the problem doesn't reproduce. The issue only applies to iBlogPro, when using any type of code/text insertion using the 'pre' tags. The problem appears to be with the rendering of the 'pre' meta tag inside the active area of the post/page. The quick way to circumvent the problem is to wrap the 'pre' tags with an extra div which will have its "overflow: auto" setting. Apparently WP-Syntax has the 'pre' tag style set to overflow: visible, which again works fine in other themes, except iBlogPro. I can also see that the iBlogPro's div corresponding to the active area of the page/post spans past the actual boundary on the right, where my side bar is showing up (as per the default iBlogPro theme setting). That's why I think the overflow: visible is not acting accordingly. I also tested with different browsers, and doesn't seem to be a browser rendering issue. Thanks for following up on this issue! Julian

Share this post


Link to post
Share on other sites
cmunns

Please link to the problem as it occurs on your site so we can see it.

Share this post


Link to post
Share on other sites
julianbalog

I removed the WP-Syntax plugin and I'm considering using a different syntax highlighter. I believe the fix would have been easier to address in the WP-syntax CSS styling than in the iBlogPro theme. For anyone having the same problem the workaround suggested in my previous post would circumvent the issue with WP-Syntax. I'll close this request and consider it resolved. Thank you.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

×