faddah

@Joe Siegler — which are you referring to? my original question about auto-posting to google+ on publish, or the fatal error when using both @raggedrobins google+ plug-in with the google connect plug-in already active?

if the original question — that is still no-go, as @raggedrobins pointed out, the google+ api allows read-only, no writing from external sources, thus far, due to their security concerns. that is likely to change in the future, but not presently. we’ll see, and i’ll continue to search for a hack and post back here if i found it.

if it’s the fatal crash with the plug-in conflict — yup, still happens. my only solution to get back where i had been was to delete @raggedrobins‘ google+ plug-in folder completely. @raggedrobins has not said if she has seen the same issue or if they are working on a fix for the conflict.

hope this helps.

i ended up deleting your “google” folder from the plug-ins directory & everything came back. evidently, your plug-in doesn’t play nice with something in the API of WP Google+ Connect, or they don’t play nice with you. one or the other

@raggedrobbins — tried installing your plug-in in my wp 3.3 blog to give it a spin. after trying to activate, now i can’t get back to my general installed plug-ins dashboard page in wp to turn it or anything else off. get:

Fatal error: Cannot redeclare class apiException in /home/one4zero/public_html/ialsowent.com/wp-content/plugins/wp-google-plus-connect/src/apiClient.php on line 45

… help, please?

@raggedrobins – fer realz? would seem to me something simple that would automatically be in the api. there are share on google+ buttons and widgets in javascript & other web languages for all manner of adding into web pages, not being able to do a post in the same way automatically seems silly not be there. i’ll look at the Google API and see if i can figure a javascript way to do it for a plug-in. btw, @raggedrobins, which plug-in is yours? url, please, so i can check it out?

thanks for offering the video town hall! looking forward to it.

1. when/how/where can we check when it will be so we can tune in?
2. at the town hall, in the new dev. features section, can you please make the first order of business to do live demo examples of how to use/access new features like Flexible Permalinks, the Post Slugs spec. characters fix, how to use/access the jQuery and jQuery UI 1.7.1 features, creating new admin screens in the WP_Screen API, and how to use the new features in the overhaul of the Editor API?

that’s what i’m looking for. thank you & looking forward to it.

ok, marking this as resolved as i didn’t quite understand how menus work, even after reading over the menu stuff here in forums and in the codex. i had to have a friend walk me through it.

for the record, i think the tabs above, not just the menu items below, should be able to to be “drag & dropped” into their positions sideways, etc.

also, there is a persistent problem with needing to do a clean refresh to see the menus updated to what i changed correctly. i am in maintenance mode, while i’m work on the blog, but don’t have any caching (Super Cache, etc.) currently activated. i’ve updated & optimized the database tables several times, but still run into this problem. any suggestions here? should i report this as a bug in 3.1.2? if so, where do i report bugs? please advise.

best,

— faddah wolf
portland, oregon

yes! yes! yes! that did it!

thank you, thank you, thank you, “L.” i’ve banged my head over and over on this one, and had given up all hope as it appeared no one was responding to what i was seeing here on the forums in this post/thread. but you came through! i’ll go back now and read the referenced link on html5 placeholder styling to fill out what i didn’t know. but, oh, thank you for this.

i still think this should be filed as some sort of bug or feature enhancement in wp 3.2.1 & the 2011 theme. where does one go to do that?

thank you again. takes some time, but the wp-dot-org forums really do come through, if you’re patient and keep at it.

best,

— faddah wolf
portland, oregon

hi david & esmi, et al.,

ah, so i’m not crazy for not seeing “searchengine.js” in there, eh? ??

i do not think this is an image, because when you do firebug, web developer or inspect element on the search field, you get:

Pseudo::-webkit-input-placeholder element          user  agent  stylesheet
input::-webkit-input-placeholder, isindex::-webkit-input-placeholder, textarea::-webkit-input-placeholder {
     color: darkGray;
}

its text as it gives that darkGray color (#A9A9A9). so it’s something in a hook somewhere in either base wordpress 3.2.1 or twentyeleven theme that make those hooks to webkit (google, safari) or mozilla (firefox, etc.).

wish a dev or dev rep for WP would chime in as to what is going on here. could be a bug in how the HTML5 is being handled.

best,

— faddah wolf
portland, oregon

hi again, esmi, david, all,

well, i tried looking over what david indicated in chrome.

first of all david, where in the inspect element developer tool window are you seeing this “searchengine.js”? the main left pane? the small right pane? i have used inspect element on the search box in chrome, i’ve used the web developer extensions and firebug light, and i don’t see “searchengine.js.”

but i went searching for such a javascript file throughout all of my wordpress 3.2.1 install, in all of the base install and in the twentyeleven parent them (i don’t have any javascript yet in my child theme). throughout all, there is no “searchengine.js” in there.

i also opened and examine the package content of the google chrome app, and found nothing in there either named “searchengine.js.”

so i’m at a loss on were to look for this file to make any changes to it that will change the color in chrome’s webkit.

any further help here would be appreciated. for now my only workaround is to make the search box background a different color so you can see the “Search” placeholder text a wee bit better, but the weak gray there still is not all that readable.

best,

— faddah wolf
portland, oregon

hi again, esmi,

so i deactivated wp super cache and emptied the cache in my safari browser and reloaded the page. i’m still getting the old darkGray (#A9A9A9), not the super dark gray i want in that Search field (#303030).

to make sure, i launched a new instance of the latest version of google chrome, went to the site… and this browser, which had never been to the site before, is also seeing the “Search” placeholder as #A9A9A9, not #303030.

so i’m at a loss.

again, i don’t think this was a cache or w3 validation issue — i’m just child theming selectors direct from the vanilla twentyeleven theme (that theme itself, if you run it through w3 validator, does not pass muster very well, so it’s hard to parse out what my error might be vs. what comes up in w3 validator). i really think this has to do with how google chrome & apple safari using webkit parse HTML5, as opposed to how firefox 7 using mozilla (which sees the #303030 child theme change just fine) parse the HTML5. this is evident in this bit of code relating to it in the vanilla twentyeleven style.css —

#branding #s {
	float: right;
	-webkit-transition-duration: 400ms;
	-webkit-transition-property: width, background;
	-webkit-transition-timing-function: ease;
	-moz-transition-duration: 400ms;
	-moz-transition-property: width, background;
	-moz-transition-timing-function: ease;
	-o-transition-duration: 400ms;
	-o-transition-property: width, background;
	-o-transition-timing-function: ease;
	width: 72px;
}

again, doing a child theme where you add to this —

#branding #s {
color: #303030;
}

… works in firefox 7 (mozilla), but not in google chrome or apple safari (webkit).

so again i ask, please — where do i go to change the placeholder widget color, as #branding #s will not do it?

please advise at your convenience and thank you again.

best,

— faddah wolf
portland, oregon

esmi,

thank you again. one last thing — if you have google chrome or safari, could you try in them, just to see if you see what i’m seeing. i ask because another wp/web dev friend of mine looked at it before i ever posted here, and saw the same think i am in chrome & safari and neither of us could figure out a way around it.

if you can’t because you don’t have those browsers, i understand. i really do appreciate all the help you’ve given.

best,

— faddah wolf
portland, oregon

hi esmi,

i really appreciate this help.

as to wp super cache – can i turn it off, refresh the site, and turn it back on again and that might solve it?

and just to be clear, are you saying in ie9, you are seeing the problem i describe, or ie9 is not showing the problem, as in it looks very dark gray (#303030)?

after getting specifics on this from you, i will try the validator.

thank you.

best,

— faddah wolf
portland, oregon

esmi,

thank you for looking this over.

pardon my n??b question, but i don’t understand how wp super cache is related to the HTML5 Search box widget? And if it is, are there settings i can play around with in wp super cache it that will cause the change i want?

yes, per my previous discussion with david, #branding #s is set to #303030, but may i ask which browser you used to view it with above? if you read my original post above, i say that it does work in firefox 7 (mozilla’s implementation of HTML5) but i see the problem in the latest versions of google chrome & apple safari (apple’s webkit implementation of HTML5). did you try it with the browsers that i say are problematic here?

please advise at your convenience and thank you again for looking at this.

best,

— faddah wolf
portland, oregon

hi again, esmi,

thank you for writing back.

i’ve sent you a log-in to the address posted on your profile.

please take a look when you have a chance and tell me what you think.

thank you again, in advance, for this help.

best,

— faddah wolf
portland, oregon

esmi,

thank you for responding.

the site is ialsowent.com , however, it is in maintenance mode as i want to get a whole bunch of other things tweaked before i publish & release for public viewing/consumption.

if you scroll up to my first post, i have the url to a screen shot of the site which shows what i’m talking about, plus all pertinent code.

if you still need to look at the site, please post back and i’ll create a log-in for you or something like that. if we go this route, please share a contact method for you so i can send you log-in & password so it’s not posted here publicly.

thank you for looking into this.

best,

— faddah wolf
portland, oregon