Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Provide a link to the issue and debugging will be easier.
Thread Starter
quokka
(@quokka)
Sorry Andrew, you are right..
http://www.quokka.nl/
Thanks!
Bas
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Is the issue within the dashboard?
Thread Starter
quokka
(@quokka)
No, On frontpage of the site, the post form on top..
And only in Chrome, IE and FF are OK..
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
That page is probably only visible when logged in.
Rather than compromise your theme, you can explore CSS issues by using a browser developer tool like the one built-in to Google Chrome.
Thread Starter
quokka
(@quokka)
Thanks Andrew.
Decided to go with WP project manager instead..
http://wordpress.org/extend/plugins/wedevs-project-manager/
So this isn’t resolved 🙂
I have the same issue as topic author.
http://support.infolandcms.dk/?p=post
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
@thomasdk81 Sure it was, it was resolved for the original poster.
Please post your own topic with your own details and I’m sure someone will reply if they can help you.
http://wordpress.org/support/forum/themes-and-templates#postform
Aside from it being the best way to get support for your problem this topic has been marked “resolved”. Most of the volunteers here skip those because the problem is er, resolved. 😉
i’ve have the same issue with P2 Theme…
(yes I know the topic is “resolved” – but seems people keep finding this thread and might as well get the answer)
This appears to be a bug in P2 CSS (style.css) – other form elements have width (and max-width) 97.45% while #postbox input#posttitle and #postbox input#postcitation (and .inlineediting input[type=”text”] as well) have 97.6% getting resulting in 630.5px and 631.476px. Both should be rounded to 631px… but apparently browsers do it differently.
FIX – search style.css for 97.6% and replace with 97.45%
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Don’t edit the theme’s files because you’re going to lose your changes when the theme updates.
Make your modifications through a Child Theme.
If it’s just CSS modifications, forget the Child Theme and use this Custom CSS Manager plugin to hold your CSS.
That means you’ll have to create new styles rather than modify existing styles.
You are absolutely correct – except in this case Trac ticket mentions exactly the same bug being fixed using same method… that is even listed in readme.txt, but somehow fixes in diff have not been merged into style.css, if you happen to know how to publish the fix several users would be immensly happy.
http://themes.trac.wordpress.org/changeset?old_path=/p2/1.4.1&new_path=/p2/1.4.2
btw make.wordpress.org/core uses 1.4.2-wpcom that does have this fix…
