Not sure if I did setup something wrong:

I've enabled Spamicide and enabled the field for form_id user_register_form, filled in a Spamicide directory and chose a custom FORM FIELD NAME.

Now when creating a new account I still see a empty field with a description:
To prevent automated spam submissions leave this field empty. I was expecting that this was hidden by CSS?

Also the directory name I've setup can't be found, is it not created by itself?

Can you tell me if I did setup something wrong or if this could be an bug?

Comments

herbiek’s picture

Addition: Now I see a file named <choosenfieldname>.css in the directory /home/admin/domains/<mydomain>/public_html/sites/default/files/private_files/<choosendirectoryname>
In that file the line div.edit-<choosenfieldname>-wrapper { display:none; } is visible, but the field is still visible for public.

big67’s picture

Version: 7.x-1.0-beta3 » 7.x-1.x-dev

I have the same issue.

I guess it is caused by the fact that the /private_files folder content can't be accessed by unregistered users (I am restricting permissions to registered users on my web site).

Therefore I get around this by copying the

div.edit--wrapper { display:none; }

instruction at the end of my theme css file.

herbiek’s picture

Version: 7.x-1.x-dev » 7.x-1.0-beta3

Hi Big 67,

Do you have an solution for my issue? I still stuck with the visible field that should be hidden. I'm kind of disappointed that I no contributor has at least reacted on this issue.

lipcpro’s picture

Status: Active » Postponed (maintainer needs more info)

Ive tried to install spamicide AFTER setting up a local test site with a private file system and it refused to install. It must be that you installed spamicide before setting up a private file system. In my research, you can't even check the css or js aggregation (in drupal core) without a public file system. You can have both a public and a private file system, I suggest you create a public file system just for things that need to be publicly available such as spamicide or css/js aggregation, not to mention ctools will install, but the status report states ctools can't create it's directory in a private system either.

Again, I strongly suggest that you create a public file system to go along with your private file system.

herbiek’s picture

Hi Lipcpro,

I don't understand your remark, about having a public and private filesystem. What does this have to do with the functioning of Spamicide?

I have setup a Drupal installation serving files both private and public. After that setup I noticed unwanted signups from spambots and decided to install Spamicide. How can I install Spamicide before setting up a private file system? Do I have to get rid of all the work I did on that part first?

lipcpro’s picture

Status: Postponed (maintainer needs more info) » Needs review

I just committed a force to the public system instead of the default system in the dev version, please review and comment.

herbiek’s picture

Installed the latest beta version and only difference I see is that the "empty field" is having a "title" label/string in front of it. But the field is still visible.
Do I have to do more, in order to get this working correctly?

lipcpro’s picture

You should install the latest stable release which is no longer beta, if you are still having problems go to the status report page, does it complain that it can't write to the spamicide directory? If so I would suggest disabling and re-enabling the module, otherwise you have a configuration that I am totally unaware of. There must be something else that you have going on there. I have tested every configuration I can think of and haven't been able to replicate your error.

herbiek’s picture

Version: 7.x-1.0-beta3 » 7.x-1.0

I've installed Spamicide 7.x-1.0 manually (Drupal didn't notice there was a new version) by deleting the old spamicide folder in the modules/contrib folder. Copied the new folder in that position and ran update.php (which didn't seem to do anything).

Again tried to create a new account and still see the field named "title" (which I can't change?)

Did I do something wrong or forgot during installation of the module?
PS I had the latest dev version installed before I did this action.

lipcpro’s picture

I don't understand your remark, about having a public and private filesystem. What does this have to do with the functioning of Spamicide?

If you have a private file system, spamicide's css file won't be made available because drupal won't serve up private files, not because spamicide won't provide them. Otherwise, there must be something else involved.
What is your sites address so I may see this for myself?

herbiek’s picture

Hi lipcro,

I saw a new version of your module released at 31 august. I have installed this version but the visible field that one should leave empty is still visible (with the "title" in front).
Did you find some solution for that issue?

GeduR’s picture

Maybe both issues are related: https://drupal.org/node/2077363

GeduR’s picture

Issue summary: View changes

cleaned up format a bit

tohidd’s picture

big67, thank u for your quick fix :)

herbiek’s picture

Version: 7.x-1.0 » 7.x-1.1
Issue summary: View changes
Status: Needs review » Fixed

Have disabled, un-installed Spamicide and flushed caches before re-enabled Spamicide again.
This did the trick and now the field is not visible anymore! So solved for me.

lipcpro’s picture

Assigned: Unassigned » lipcpro
tobiberlin’s picture

Version: 7.x-1.1 » 7.x-1.2

I installed the latest version and the field is still appearing - at least in user register form

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Joran Lafleuriel’s picture

Permission issue ??

I had to to manualy create de spamicide folder in sites/default/files
...then I moved all spamicide css files [ feed_me.css.... ] to this new folder...

After removing all css & javascript cache, the blank field was hidden as expected...

rajmataj’s picture

If the permissions get messed up on the spamicide directory, the fields may end up showing as visible. What I've found cures this on both 6.x and 7.x versions is to go to the administration page for Spamicide on your Drupal site, make a change to the form (like check/uncheck the "Add Spamicide administration links to forms") and save the page. Mark it back to what it previously was and save again. Now, flush the cache. The unhidden fields became hidden on two of two of the site I tried this on.

Hope that helps others.

LockeTalks’s picture

Just a friendly reminder that if you're having this issue, clear your caches before you do anything else. In my case, the solution was as simple as that.