redsand

Hi gianky69,

To edit your rating, just go to: https://wordpress.org/support/view/plugin-reviews/wp-spamshield#postform

You can change the headline, the content, the rating whatever. When you’re done, just hit “Edit Post”.

If you ever need help in the future, we are happy to help. Just use the support methods mentioned above. 🙂

– Scott

Glad to hear you got things sorted out. I would however recommend modfiying your solution just a bit.

It’s generally best to be as specific as possible to prevent collisions. Use unique ID or class elements, and use the DOM tree. (See this: DOM + CSS = A beautiful couple) With the DOM, you can isolate any element on a page whether or not is has an ID or class…it is extremely powerful. Start with a known ID or class and work down from there.

The form ID is “wpss_contact_form”, but you haven’t included that, so I would recommend adding it.

If you just want to modify your current solution as-is:

#wpss_contact_form p:nth-last-child(2)  { css declarations go here... }

As you mentioned though, this could change in the future, so I probably wouldn’t recommend using “nth-last-child”. (Not likely anytime soon, but just to be safe.) That’s up to you though. When you’re using it with code you’re written and can control, you’re fine, but with plugins, themes, frameworks, etc that are updated outside your control, you should get more specific to prevent your CSS from breaking in the future.

(Before we go further, a handy plugin for adding CSS to a specific page or post is: WP Add Custom CSS.)

Browser developer consoles can help you isolate the exact DOM-based CSS selector you need. For example in Chrome, if you open your console, go to Elements, and pick the element you want to style, it literally lists the selectors out for you in a horizontal bar right below the source code.

Sometimes to select the text you want, the trick is to make sure you have styling for the text you’re not targeting. Then you can use a straightforward rule for the text you do want to target.

The text you’re trying to style is the only text not within a label. So make sure you set style rules for the text within labels as well. (The text above each input line, etc.) For example:

#wpss_contact_form p label { css declarations go here... }

Now when you set this directive for the text you want to target (“Required fields are marked *”), you can use a fairly simple selector set, that won’t have any collisions:

#wpss_contact_form p { css declarations go here... }

Some other selectors you could use:

#wpss_contact_form p label strong { css declarations go here... }

#wpss_contact_form p label input { css declarations go here... }

And since you’re not a fan of the non-breaking space in the last <p>, you can use the “nth-last-child(1)” selector with a “line-height: 0” declaration to make it disappear altogether if you like. (There are a number of ways to handle this.) Something like this would be a quick fix:

#wpss_contact_form p:nth-last-child(1) {
     line-height: 0;
     other css declarations go here...;
}

When using CSS + DOM, possibilities are pretty much endless.

I’ll add some of this to the documentation in case it’s helpful to others.

@oseven,

I’m sorry to hear that. However it’s important to remember that humans do make mistakes from time to time…and we do keep this to a minimum. If you see from our support record and user ratings, it’s extremely rare. Even the most popular plugins have had issues from time to time. The issue only existed for 2 days, and we fixed it as quick as humanly possible…about 2 hours from the time it was reported. Not many plugin authors make fixes that quickly.

Hi voltronik,

Thanks for reporting this. That’s a legitimate bug, and a fix is in progress. We’ll have a new release out shortly with the fix.

– Scott

Hi chaoti,

I’m sorry to hear about the issue you’re having and I’ll be happy to help.

If your site had an issue with the last update, then there is likely a configuration issue or conflict specific to your site. We will be happy to help you fix that.

If you haven’t had a chance to yet, please take a few minutes to work through the Troubleshooting Guide and FAQs, as these solve 90% of issues users have.

If those don’t solve the issue for you, we’ll need a bit more info from you on the specifics, and we’ll need to email back and forth, so please head over to the WP-SpamShield Support Form, and take a moment to fill out a support request. That will allow us to take care of this as quickly as possible for you.

– Scott

Not sure if you’re getting my emails. Please check your email spam folder. Anyway, the issue is that the plugin is active on the main site, but not on the sub-site. That’s why you’re not getting spam on the main site, but are getting spam on the sub-site. All the moderation notices you forwarded me are from the site where the plugin is not active.

No spam is actually “getting through” the plugin…because it’s not activated.

Once you activate it on the sub-site, it will stop your spam problem.