Some suggestions | Peter's Custom Anti-Spam for WordPress | Forum
Back to the custom anti-spam plugin page
Log In
Home
Topic RSS
12:02 pm
Great plugin, thanks for all your hard work. I'd just like to offer some suggestions for your consideration:
- Remember settings after update (not sure if this was a bug tho to be honest - my settings appeared to be lost after updating just now - i need to re upload my fonts and relist them along with my words on the admin panel
- Automatically detect fonts in font folder. If you don't want to do it for each load, perhaps have a button on the admin panel. Saves having make the list manually
- Have an option to overwrite word list with the new list on update
- Have an option to automatically generate an alphanumerical string instead of using words from the list
Thanks for your time and efforts, they are most appreciated :-)
1:28 am
Offline
Thanks for your feedback. I'm currently trying to figure out the best way to cope with the WordPress automatic plugin upgrade system. I thought it would just overwrite existing files with the same name, but it seems to just wipe out the entire folder and then re-extract the new zip file. Not cool at all. I'm open to suggestions -- my current thought is to house the fonts and other changeable files in a different directory.
I'm not sure what you mean by overwriting the word list with the new list. People are always requesting to keep their old lists when they upgrade... a problem related to the automatic upgrade system above :(
I like the "button for automatically detecting fonts" idea. I'll put it on my rainy day list. Code contributions are certainly welcome.
As for the automatic generation of alphanumeric strings, have you looked at the random anti-spam version? It's a couple of minor versions behind the custom anti-spam release, but it uses the same framework.
9:05 am
Thanks for the reply. Yeah I think moving the fonts else where is your only option with the automatic updates really, perhaps include the default set you supply in the plugin's folder, but have another location that you can check for the existence of extra/alternative fonts (pretty easy with scandir in php5, and there's some suggestions for php4 on the scandir page).
Sorry I didn't realise the overwriting of the word list was related to the automatic update problems. I always assumed that you changed the words on update as a security measure, so my thought was to make this behaviour optional. The problem of automatic updates overwriting the word list could be overcome by simply migrating the words to an option like the rest of the settings.
Yeah I haven't really checked out all the different branches yet, thanks for the suggestion.
Let me know if you'd like any help with the checking for fonts thing, I'd be willing to throw something together when I get the chance ;-)
Thanks again for all your hard work
4:06 pm
Offline
Hi Dave,
Thanks for your help here. I'll need to find the time to do a complete analysis of the plugin's file structure.
I like the idea of forcing users to create a separate folder to house their custom changes. Here's a first outline:
wp-content/plugins/peters-custom-anti-spam-image
- this would be the core of the plugin with default settings that are always overwritten
wp-content/plugins/anti-spam-mods
- in the base of this folder would be:
-- translations (maybe using the .po and .mo standards)
-- settings file
-- custom word list
- it would also have a "fonts" folder
- I'm not sure what to do about the audio files yet. That would depend on how WordPress handles locales.
This makes the initial installation of the plugin more involved, but has long-run benefits and works around the automatic plugin upgrade system... that is until they change that system (*insert angry face*). For now I'm just advising people to manually upgrade :)
10:12 am
I have installed your plugin and seems to work very well into WP 2.7.1
One question is if you will plan to code your plugin in a way it will interact with other plugins like qTranslate.
qTranslate works perfectly but it requires some kind of output to work.
7:51 pm
Offline
Thanks for the suggestion, Riccardo. My plan is to eventually (not sure when) use the standard _e() and __() functions for strings, which would standardize the plugin for .mo and .po files. If qTranslate works with those standards, then that would work out well.
