billseymour

@Mike-

Re the 4.0.10 Changelog saying:
Bug fix: Field default text was not showing in form.

If this fix was re the Placeholder text not appearing in IE, I wanted to report that in IE8 (which is what I am using to test), the Placeholder text still does not appear. (To get the Placeholder text, a jQ or JS function is still necessary).

Not a complaint – just trying to provide running feedback.

For those who might need a solution immediately, this shim works for me (it took a bit of fiddling, but does work) – Placeholder text appears in ie8, where I just tested it):
https://github.com/mathiasbynens/jquery-placeholder

@mike –
Thanks (as always) for your responsiveness. I imagine ‘time’ is a bit short during the shakeout of a major release such as this. BTW, overall I have generally had no problems with 4.0.6 – mostly a matter of making some adjustments relating to Classes (textarea, in particular).

Great job!

@Mike-

I did a little digging, and here is the answer:

ref to comment answer: https://css-tricks.com/snippets/css/style-placeholder-text/#comment-267934 – the commenter, Thibaut, says:

Firefox 19 lowers the opacity of the placeholder to 0.54 by default.
To get the correct color you need to reset it:
::-moz-placeholder { opacity: 1; color: red; }

I am using Firefox, and with this Opacity:1 style I get fully transparent color. Hopefully this will be of help if anyone else runs into the same situation. –Bill

Glad to help. Thanks for great plugin.

Hello, just got back from vacation and self-imposed ‘no technology’.

I am just trying the plugin out on a xampp localhost installation, so nothing to show you right now (I can put something up if necessary).

However: I located the problem: My child theme line-height setting (line-height:25px) results in a timer ‘box’ that is 27px tall. So the timer text (10px) is now inside a taller box. The postion:absolute placement in the plugin probably assumes that this text will be flush to the top – with the unexpected taller box, my resulting timer text sits ‘lower’ than intended, and so touches the progress bar.

By adding this to my style sheet, the timer text is now in the proper position:

.codeart-google-mp3-player div.controls .timer {
   line-height: 1;
 }

Possibly you might want to include a specific line-height in the plugin’s Css, to override a more general setting? I hope this was helpful – I can put up a test page online if you’d like.

I just started using Types, and I think the plugin is terrific.

I was unable to find a way to display a Taxonomy in a column in Admin. Has this feature been included in Types yet? (I see from this post that this was the plan).

If it has not been included yet, then I would certainly recommend adding this capability. Thanks for any information.

No, not quite what I have.

This is what I am seeing:

– Visual editor – No AddQT buttons on any editor page (not Pages, nor Posts) (I have the buttons checked for Visual editor in QT setup page)

– HTML editor, Posts and Pages – AddQT buttons appear

– HTML editor, Custom Post Types – No AddQT buttons

Also: I tested using Custom Post Types created via functions.php, just to be sure that the problem was not Types plugin. I don’t get AddQT buttons showing up for either form of CPT.

In case my computer setup is of importance:
Windows Vista, 32 bit, Firefox (latest), WordPress (3.5.1)

I hope that this info helps.

Thanks for the reply Frank.

I checked things again:
AddQT is working fine in Pages and Posts.

I have two Custom Post Types (created with the Types plugin) – in the case of the HTML editor for these CPT’s, the basic buttons appear, but the AddQT buttons do not appear.

Sorry for misstating the situation. Should the plugin add quicktags when adding content to CPTs? (If ‘yes’, then perhaps there is a conflict when I use Types plugin).

My experience: If I uncheck the boxes, when I Save the widget settings, the boxes are checked again. Definitely a bug, appreciate the anticipated fix.

+1 that widgets must somehow be locked in for a particular theme. The way things stand now, widgets are a “reconstruction project” waiting to happen the moment one changes themes.

Also – it would also help a great deal if any “logic” associated with a widget (such as Widget Logic) could also be saved. Right now, even when widgets are reset in a theme, the logic must also be reconstructed.

Any improvements in this area would be most welcome.

@frank –
I checked my exported AddTags file, and I saw that the checkbox information was in the file, as you said. However, when I imported that file into an existing AddTags active installation, while the Tags imported successfully, the boxes remained unchecked.

I may be doing something wrong, just providing you with some feedback. Thanks.

Re the checkboxes, any of three improvements would be helpful:
– default is all boxes checked (as mentioned earlier in this thread)
or
– a “check all boxes” option
or
– Export to also include all the checkboxes as well – so that when I upload from local site to online, the AddQuicktags file also imports the checkboxes as well.

Excellent plugin, great work.

Good to know that the features exist in the Advanced product. I will likely look into the Advanced PTO. Thanks for the quick response.

OK, I think I’ve isolated it.

I get the ‘menu item highlighted’ effect if I have Relevanssi option ‘Highlight query terms in result titles’ checked.

When I uncheck ‘Highlight query terms in result titles’, there is no menu item highlighted if the search term is in the menu.

Thanks for looking into this. –Bill

My highlight options:
——————–
highlight terms: BG color
Highlight query terms in result titles – checked
highlight in documents – checked
in comments – Unchecked
uncheck if non-ASCII – checked
text color highlights #ff0000
bg color for highlights #ceddf2
css style for highlights background: #ceddf2
——————–