A question I’m asked often is whether FP supports or not having multiple users; well, in short, the answer is no.
The long answer is you may run multiple times the setup and choosing a different username and password; this way you would get one user for each time setup was run.
Why hiding so well such a feature? Well, every user would get administrative powers, so I thought it was better not making it world-available, you know. :)
So, use it at your own risk.
I’ll work on a three-level system, but at the moment I want to focus on more important features and on polishing the core.
The other question is about translating plugins.
Today I was asked if SPB system wasn’t better, as they put all of their language files in the same directory. Well, SPB does not have a plugin system, and even if it did it would be probably self-contained.
By the way, I thought about a way to put everything in the main lang/ directory. The problem is plugins should really NOT depend on anything coming from a clean installation, so a plugin developer should package his work this way (notice that directory structure for plugins changed in 0.702 version):
[fp-interface] [lang] [en-us] lang.plugin.PLUGINNAME.php [other-lang] lang.plugin.PLUGINNAME.php [fp-plugins] [PLUGINNAME] plugin.PLUGINNAME.php [res] [tpls]
So that you, as a user, would upload just the whole directory tree without having to think about the dir structure.
You can understand that just having
[PLUGINNAME] plugin.PLUGINNAME.php [res] [tpls] [lang]
would be easier for both the maintainer and the user; the maintainer would package only one directory for each plugin, and the user would upload only that directory.
I know this would make life for the plugin dev more complicated, but on the other hand I can’t find anything better :/
PS: do you like the new graphics on this web page? (Shit+F5 if you don’t see anything new)