Quote from: Scotty at Nov 14, 2006, 07:46 AM
Quote from: banzai at Nov 14, 2006, 06:29 AM
Scotty I still have the same issue of diggidis
This does not appear to be a valid MODx Resource Wizard package.
Tryied with two different server 
Banzai,
did you try applying the fix that Jesster444 submitted?
http://modxcms.com/forums/index.php/topic,8182.msg63227.html#msg63227
-sD-
Thanks now works great
-
☆ A M B ☆
- 24,524 Posts
Well that is certainly smooth and professional enough! Excellent job, ScottyD
(the "helper" document sys_evt.html is in the wizard/tpl folder, not the wizard/ folder per line 116 of forms.tpl, so it causes a 404 error)
-
☆ A M B ☆
- 24,524 Posts
No problem at all. I just unzipped your php file, uploaded it to my root (sottwell.com) and ran it from the browser. Fast and smooth. I immediately started clicking on things (which is why I re-design my site so often!) and that’s how I ran across the little error in the path for that helper file. Oh, and anybody who’s interested can go and look at it in my guest manager login.
What do you want to bet that there will be somebody complaining about having to upload the one file
I do have a question, though. Is it possible to download the whole thing and install it manually, for the paranoid amongst us?
-
☆ A M B ☆
- 24,524 Posts
I would also like to see the self-check be a configuration parameter so that it can be turned off if desired.
I added this bit at line 148 in the module itself:
if($selfcheck) {
print $mrw->wizard_selfcheck($ver, $_getlang);
}
and added the &selfcheck=Selfcheck;int;0 in the module’s configuration. Would probably be better as a button/link or something, though.
-
☆ A M B ☆
- 24,524 Posts
Hmmm... I see a request feature! If the snippet/module needs extra database tables, there could be a field for entering the sql for creating the tables and then part of the install process would be to create the tables.
See, there’s no pleasing women!
I dislike those modules that check for the existence of a table every time they run.
However, if this installer thing could just let you run a separate ’execute once’ script during installation, that script could add db tables, extra fields or whatever. So snippets/modules that check and create could just move that bit out to a second script which is executed during installation, and everyone’s happy. Total flexibility for the snippet/module author, no complication in MRW, no un-necessary db queries every time the snippet/module is run.
Well, I think I have an idea on how to solve this.
I could add another text area in the "Make new package" form for sql code.
It could then generate an optional file ("query.sql" for example) that would be packaged with the resource.
If MRW finds this file, it will execute it on install.
The resouce creator could use the string "[dbpre]" in their sql code and I could have MRW do a str_replace to put in the actual database prefix.<br />this way the sql could be as simple or as complex as the creator needs it to be.<br /><br />What do you guys think?<br /><br />(and since it is easy to miss, the latest dl is attached to this post):<br />http://modxcms.com/forums/index.php/topic,8182.0.html<br /><br />-sD-<br />Dr. Scotty Delicious, Scientist.
