Hi, I have modified the editpage.php to present different things when you edit (screen 1-->screen 2-->screen 3).
I've not "chained" between themselves: the problem is that it seems that when I submit, doesn't know it: using wgout to see state of vars I see always the formtype is initial (before I did this "multiple-edit", it went well; maybe it's impossible this "multiple-edit").
I am looking for a debugger for php and so see what's going on, but I don't know any (I will try gubed). Hoewever, if you know multiple edit (that is, the editpage.php shows things depending of $current_screen...and by the way, the value is not modified also, so it's the form and the vars, just seems that the recall to edit doesn't remember the globals)
In short: does editpage.php remember global values when call again to editform()?
Lot of thanks!
Jordi
On 5/9/05, Jordi Domingo jordidr@gmail.com wrote:
Hi, I have modified the editpage.php to present different things when you edit (screen 1-->screen 2-->screen 3).
I've not "chained" between themselves: the problem is that it seems that when I submit, doesn't know it: using wgout to see state of vars I see always the formtype is initial (before I did this "multiple-edit", it went well; maybe it's impossible this "multiple-edit").
I am looking for a debugger for php and so see what's going on, but I don't know any (I will try gubed). Hoewever, if you know multiple edit (that is, the editpage.php shows things depending of $current_screen...and by the way, the value is not modified also, so it's the form and the vars, just seems that the recall to edit doesn't remember the globals)
In short: does editpage.php remember global values when call again to editform()?
Yes, but not between requests.
The hidden-input should have worked. You may also want to try special actions.
-- Jamie ------------------------------------------------------------------- http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB.
Jordi,
I set up form-based input to work with MediaWiki--login sequence over several screens including a survey and a form so users can type just the content but the result is a wiki page with links and back-links. I found the model used in SpecialUserLogin (which leverages a template in /includes/templates) to be the easiest one to work with. Just model the constructor, the execute() function and the LoginForm () function--you can really ignore all the rest.
Hope this helps.
Con Rodi Center for Human-Computer Interaction Virginia Tech
On May 10, 2005, at 8:36 PM, Jamie Bliss wrote:
On 5/9/05, Jordi Domingo jordidr@gmail.com wrote:
Hi, I have modified the editpage.php to present different things when you edit (screen 1-->screen 2-->screen 3).
I've not "chained" between themselves: the problem is that it seems that when I submit, doesn't know it: using wgout to see state of vars I see always the formtype is initial (before I did this "multiple-edit", it went well; maybe it's impossible this "multiple-edit").
I am looking for a debugger for php and so see what's going on, but I don't know any (I will try gubed). Hoewever, if you know multiple edit (that is, the editpage.php shows things depending of $current_screen...and by the way, the value is not modified also, so it's the form and the vars, just seems that the recall to edit doesn't remember the globals)
In short: does editpage.php remember global values when call again to editform()?
Yes, but not between requests.
The hidden-input should have worked. You may also want to try special actions.
-- Jamie
http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB. _______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Con, Jamie, thanks.
First I will ensure hidden in the forms is correct, and then I will try the SpecialUserLogin -- it seems a similar sequence-of-screens to my aim.
Jordi
P:S.:it seems that I sent this message two times at the list, one with form problem and other with form/globals problem. My mail gestor said it couldn't sent it, so I re-sent it after changing the subject, but seems it received both..sorry.
On 5/11/05, Con Rodi conrodi@vt.edu wrote:
Jordi,
I set up form-based input to work with MediaWiki--login sequence over several screens including a survey and a form so users can type just the content but the result is a wiki page with links and back-links. I found the model used in SpecialUserLogin (which leverages a template in /includes/templates) to be the easiest one to work with. Just model the constructor, the execute() function and the LoginForm () function--you can really ignore all the rest.
Hope this helps.
Con Rodi Center for Human-Computer Interaction Virginia Tech
On May 10, 2005, at 8:36 PM, Jamie Bliss wrote:
On 5/9/05, Jordi Domingo jordidr@gmail.com wrote:
Hi, I have modified the editpage.php to present different things when you edit (screen 1-->screen 2-->screen 3).
I've not "chained" between themselves: the problem is that it seems that when I submit, doesn't know it: using wgout to see state of vars I see always the formtype is initial (before I did this "multiple-edit", it went well; maybe it's impossible this "multiple-edit").
I am looking for a debugger for php and so see what's going on, but I don't know any (I will try gubed). Hoewever, if you know multiple edit (that is, the editpage.php shows things depending of $current_screen...and by the way, the value is not modified also, so it's the form and the vars, just seems that the recall to edit doesn't remember the globals)
In short: does editpage.php remember global values when call again to editform()?
Yes, but not between requests.
The hidden-input should have worked. You may also want to try special actions.
-- Jamie
http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB. _______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
This is a question of a different nature about "forms" and "templates" I could not find it in the FAQ, so I must be looking for the wrong sort of answer.
What I want to do is create a non-transclusive template. The MW "template" concept is a transclusion, so that won't fit my requirement. I am looking to create a type of article template with certain pre-defined headers and sub-headers that authors can choose for convenience. To resort to an analogy that is often abused in computing, let's call it a "car form." Users can invoke a form with headings like "style", "history", "specifications", "safety", and appropriate sub-headings. Having invoked the form to create a new article, they are completely free to customize in whatever manner they believe suits the needs of the article.
What is this entity in MediaWiki and how do I go about employing it?
Thanks, Carlton
Carlton B (carltonb@mindspring.com) [050511 17:04]:
This is a question of a different nature about "forms" and "templates" I could not find it in the FAQ, so I must be looking for the wrong sort of answer. What I want to do is create a non-transclusive template. The MW "template" concept is a transclusion, so that won't fit my requirement. I am looking to create a type of article template with certain pre-defined headers and sub-headers that authors can choose for convenience. To resort to an analogy that is often abused in computing, let's call it a "car form." Users can invoke a form with headings like "style", "history", "specifications", "safety", and appropriate sub-headings. Having invoked the form to create a new article, they are completely free to customize in whatever manner they believe suits the needs of the article. What is this entity in MediaWiki and how do I go about employing it?
When I want to do something like this on Wikipedia, I enter {{subst:template}} - rather than {{template}}. Then save. Then edit and tweak. Though this is almost certainly not as automated a process as you're looking for.
- d.
On FIRSTwiki, we just have format pages, and copy/paste the source.
On 5/11/05, Carlton B carltonb@mindspring.com wrote:
This is a question of a different nature about "forms" and "templates" I could not find it in the FAQ, so I must be looking for the wrong sort of answer.
What I want to do is create a non-transclusive template. The MW "template" concept is a transclusion, so that won't fit my requirement. I am looking to create a type of article template with certain pre-defined headers and sub-headers that authors can choose for convenience. To resort to an analogy that is often abused in computing, let's call it a "car form." Users can invoke a form with headings like "style", "history", "specifications", "safety", and appropriate sub-headings. Having invoked the form to create a new article, they are completely free to customize in whatever manner they believe suits the needs of the article.
What is this entity in MediaWiki and how do I go about employing it?
Thanks, Carlton
MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
At Yellowikis we've added our own button to the "edit bar" (next to the buttons for bold, italic, links, image, etc) that inserts a preformatted "template" text of headers and advice - you can add as many buttons as you want to the edit bar.
You do this by changing the "toolarray" elements of the EditPage file which you find in the Includes directory - let me know if you want to know more about how to do this.
Paul
On 5/14/05, Jamie Bliss astronouth7303@gmail.com wrote:
On FIRSTwiki, we just have format pages, and copy/paste the source.
On 5/11/05, Carlton B carltonb@mindspring.com wrote:
This is a question of a different nature about "forms" and "templates" I could not find it in the FAQ, so I must be looking for the wrong sort of answer.
What I want to do is create a non-transclusive template. The MW "template" concept is a transclusion, so that won't fit my requirement. I am looking to create a type of article template with certain pre-defined headers and sub-headers that authors can choose for convenience. To resort to an analogy that is often abused in computing, let's call it a "car form." Users can invoke a form with headings like "style", "history", "specifications", "safety", and appropriate sub-headings. Having invoked the form to create a new article, they are completely free to customize in whatever manner they believe suits the needs of the article.
What is this entity in MediaWiki and how do I go about employing it?
Thanks, Carlton
MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
--
http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB. _______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Thank you, this and the previous suggestion about {{subst:template}} were what I was looking for. If I decide to put it on the toolbar and can't figure it out, I'll get in touch.
-Carlton
-----Original Message----- From: mediawiki-l-bounces@Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org]On Behalf Of admin Yellowikis Sent: Sunday, May 15, 2005 1:32 AM To: Jamie Bliss; MediaWiki announcements and site admin list Subject: Re: [Mediawiki-l] Different "form" question
At Yellowikis we've added our own button to the "edit bar" (next to the buttons for bold, italic, links, image, etc) that inserts a preformatted "template" text of headers and advice - you can add as many buttons as you want to the edit bar.
You do this by changing the "toolarray" elements of the EditPage file which you find in the Includes directory - let me know if you want to know more about how to do this.
Paul
On 5/14/05, Jamie Bliss astronouth7303@gmail.com wrote:
On FIRSTwiki, we just have format pages, and copy/paste the source.
On 5/11/05, Carlton B carltonb@mindspring.com wrote:
This is a question of a different nature about "forms" and
"templates" I
could not find it in the FAQ, so I must be looking for the
wrong sort of
answer.
What I want to do is create a non-transclusive template. The
MW "template"
concept is a transclusion, so that won't fit my requirement.
I am looking
to create a type of article template with certain pre-defined
headers and
sub-headers that authors can choose for convenience. To resort to an analogy that is often abused in computing, let's call it a "car form." Users can invoke a form with headings like "style", "history", "specifications", "safety", and appropriate sub-headings.
Having invoked
the form to create a new article, they are completely free to
customize in
whatever manner they believe suits the needs of the article.
What is this entity in MediaWiki and how do I go about employing it?
Thanks, Carlton
MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
--
http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB. _______________________________________________ MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Ok, in my reunion with my project bosses they said me just called form editpage to other editpage2 and this to editpage3, if possible. I'll try and if not, back to llok the specialuserlogin.
By the way, finally I know the form "not save now" problem: I made some modifications i article.php also, but I moved them to article.php to better maintenance. However, that made that laodcontent loaded the original text and didn't change it. So, I'll have to made not only editpage.php-->edit2.php-->edit3.php, but also article.php-->article2-->article3, I think. Oh well. However, as the form problem seems solved, probably I'll can pass the parameters as hidden atributes in the form. I suppose the main problem will be sure it calls correctly.
Thanks!
Jordi
mediawiki-l@lists.wikimedia.org