Closed (won't fix)
Project:
Logo Tool
Version:
7.x-2.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Jul 2011 at 23:57 UTC
Updated:
8 Jul 2011 at 11:47 UTC
wtf?
Error message at installing
Comments
Comment #1
pobster commentedI love acronyms here's another.
RTFM.
Pobster
Comment #2
pobster commentedIncidentally, any time you wish to write "wtf" in a support ticket for free software please check I'm not the author.
Have a nice day.
Pobster
Comment #3
caravinci commentedGreetings pobster
you're absolutely right: my informality, rudeness and lack of detail is inexcusable and I apologize for that. I'm sorry.
On the other hand, it does not change the fact that there was a problem, and in it's quality of free software I decided to come here and post a bug for solution, not trying only to help solve my problem (which ultimately is not the goal- I obviously worked my way around in some other fashion). I guess I shouldn't have even bothered. Also, if you're not the Author, you're name is by mistake right next to the module's title on the project's page... it should be changed accordingly so that you won't ever be bothered again by this or any other issues.
Also, more on a personal opinion, not that you ask or care about it... the utter lack of relationship of your complaint to the actual solution to the problem and your "atypical" reply doesn't help either the project nor the community... and It's not going to make me look worse or you better.
There's still an installation issue with your somebody-else's module.
Thanks for your attention and please excuse these unnecessary but pertinent (as was your reply) drama.
Comment #4
caravinci commentedNow, *clear voice*
I mean to say...
"what is this!?"
got this message right after installing your (or whoever's) module, any ideas? it may need some looking into.
I'd go to 'admin/config/system/logotool' as TFM states, but there's no such page...
it also locked up my site and had to manually remove the module via database access in order to get it back
any ideas?
Comment #5
pobster commentedThe only issue here is that you're using a *development version* of a module which was ported well before the D7 API had stabilised (it's from like Feb 2010).
The reason for these particular errors is that (fairly near to D7 launch) it became no longer necessary to run drupal_install_schema/ drupal_uninstall_schema - if you have a hook_schema then they're run automatically (rightly as they should be). If you want to remove these lines from the .install file then I'm sure you'll probably get to another API error a little bit further along.
Good luck with that.
Pobster
PS. If you think I'm going to help you any further with this then you're quite mistaken; please don't bother reopening this ticket unless you're posting a patch - link to the 'manual': http://api.drupal.org/api/drupal
Comment #6
pobster commentedBTW, yes when something is inexcusable then it's unlikely to be excused...
Pobster