Short story….

When I try to post a comment here:

http://fervorflower.com/index.php/gallery/image_full/13/

I get this error:

MySQL ERROR:

Query: SELECT blacklisted_value, blacklisted_type FROM exp_blacklisted WHERE blacklisted_type = ‘url’ OR blacklisted_type = ‘ip’

I’m not using a white or blacklist. Eventually I want to set it so only “approved” accounts are allowed to post or comment or leave trackbacks.

I’m not opposed to whitelisting. But this module isn’t even installed. I do have commenting turned on, I am required you be a member. This error occurs from both my admin and my test user account regardless of whether I “preview” or “submit” the comment.

Help?

That’s the rub.

Long story….

I am trying to redesign this site:

http://amesslam.org/

from the ugly, non functional, too-messed-up-to-clean-up-site that no one uses, to something I can be proud of.

And rather than trying to upgrade, I figured I’d start from scratch. It should just be a matter of pointing the URL to the new files and database (I hope). I am not worried about migrating any data or users. I’m the only person who did much posting to the old site, and the users are all people who come to our events. And while yes, technically, I am probably in license violation, the testing site isn’t public facing, I’m not promoting it, and I promise that when I pull the trigger the old one will go away. Then my test site will be used for something else.

Any recommendations would be helpful. I thought of doing this entirely offline, but then no one could see my examples.

Odd- try installing the blacklist module (go to ‘Modules’ tab, click install).  Basically, that will create the table that’s missing according to your error message.  So for now- quickest way to get around the problem.  And it’s probably a good idea to enable the blacklist regardless.  Actually- that’s definitely a good idea.

That said, seems to me you should be able to not enable it- or we need to make a note in the docs that it’s required.  What version/build are you running on, I’ll give the development crew a ‘heads up’ on the issue.

(And yea, I always had my test install online as well- for a ton of reasons.)

Running 1.4.2 downloaded it three (?) days ago.

I’ll fire up the blacklist, though I’m not sure why it’s needed if I only allow people I know. Will look into what it does more.

It’s useful to help block spammers, mainly.  They can be real pests and slow your site down when spam bots hit it.  If you keep an up-to-date blacklist and have it write to .htaccess it keeps the blocked spiders from ever hitting the dynamic side of your site.  It’s definitely a good idea to use it- but it shouldn’t throw errors if you choose not to.  I’ll put in a report on it for sure.

Well, I can leave comments now. I added my license to the config.php file.

I did notice that the submission box changed. Before you had an area for name, email, etc. Now you just get the comment box. I do intend the site to be just for people who go to the event (or used to). It doesn’t have many members, but hopefully the site will eventually be a place for those forced to leave to keep up with the left behind.

It’s getting there.

Ah- the comment submission form’s appearance will change if you’re logged in (well, if your templates are set that way).  For logged in members, no sense making them add info that’s already in the database- so it doesn’t show the fields for stuff like name, email, etc.

- glad you’re making progress.

I should have been logged in when testing the comments. Did as both admin and test user. Since I’d turned on the members only commenting, but still got the logged out form, figured that might have been a useful datapoint on the error.

Now I am deleting all the files I tested with.

Maybe people don’t do this often, but it would be cool if there were a batch remove.

I’ve got to weeks to get this done and make the cut-over. If I miss that deadline I am punished with another 4 weeks of time! Heh. I’d like to launch it and promote it in August, but if I miss that, the following month will be cool as well.