Hello,
I need to be able to trace trough my wiki processing and followed http://www.mediawiki.org/wiki/How_to_debug instructions to setup the debug. However, the wfProfileIn & wfProfileOut calls in $wikiroot/includes/WebStart.php are causing undefined function errors. Can someone tell me what is the problem? Thank you.
Nelson
Computer Sciences Corporation Registered Office: 2100 East Grand Avenue, El Segundo California 90245, USA Registered in USA No: C-489-59
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi Nelson,
These are the steps I've found for using profiling. It doesn't seem to be the most straight-forward process.
Add the profile database in wiki/maintenance/archives/patch-profiling.php
Then change LocalSettings.php adding the line $wgProfileToDatabase = true;
change the line $wgEnableProfileInfo = true; to true in AdminSettings.php
In StartProfiler.php comment the first line and uncomment the second two.
Hope that helps. By the by, you would probably get more help for this problem on WikiTech.
-Courtney
-----Original Message----- From: mediawiki-l-bounces@lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Nelson A Li Sent: Thursday, December 13, 2007 3:38 PM To: MediaWiki announcements and site admin list Subject: Re: [Mediawiki-l] How to debug
Hello,
I need to be able to trace trough my wiki processing and followed http://www.mediawiki.org/wiki/How_to_debug instructions to setup the debug. However, the wfProfileIn & wfProfileOut calls in $wikiroot/includes/WebStart.php are causing undefined function errors. Can someone tell me what is the problem? Thank you.
Nelson
Computer Sciences Corporation Registered Office: 2100 East Grand Avenue, El Segundo California 90245, USA Registered in USA No: C-489-59
------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------------------------------------------
_______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Thank you, Christensen. Although I don't know how to "add theprofile database", I will take a look of "maintenance/archives/patch-profiling.php" to see if I can learn something. If still no clue, I will try wikitech.
Nelson
Computer Sciences Corporation Registered Office: 2100 East Grand Avenue, El Segundo California 90245, USA Registered in USA No: C-489-59
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"Christensen, Courtney" <ChristensenC@BAT To TELLE.ORG> MediaWiki announcements and site Sent by: admin list mediawiki-l-bounc mediawiki-l@lists.wikimedia.org es@lists.wikimedi cc a.org Subject Re: [Mediawiki-l] How to debug 12/18/2007 08:36 AM
Please respond to MediaWiki announcements and site admin list <mediawiki-l@list s.wikimedia.org>
Hi Nelson,
These are the steps I've found for using profiling. It doesn't seem to be the most straight-forward process.
Add the profile database in wiki/maintenance/archives/patch-profiling.php
Then change LocalSettings.php adding the line $wgProfileToDatabase = true;
change the line $wgEnableProfileInfo = true; to true in AdminSettings.php
In StartProfiler.php comment the first line and uncomment the second two.
Hope that helps. By the by, you would probably get more help for this problem on WikiTech.
-Courtney
-----Original Message----- From: mediawiki-l-bounces@lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Nelson A Li Sent: Thursday, December 13, 2007 3:38 PM To: MediaWiki announcements and site admin list Subject: Re: [Mediawiki-l] How to debug
Hello,
I need to be able to trace trough my wiki processing and followed http://www.mediawiki.org/wiki/How_to_debug instructions to setup the debug. However, the wfProfileIn & wfProfileOut calls in $wikiroot/includes/WebStart.php are causing undefined function errors. Can someone tell me what is the problem? Thank you.
Nelson
Computer Sciences Corporation Registered Office: 2100 East Grand Avenue, El Segundo California 90245, USA Registered in USA No: C-489-59
------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ------------------------------------------------------------------------ ------------------------------------------------------------------------ ----------------------------------------------------------------
_______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
_______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Hello,
My problem: 1. I created a table in my wikidb and pre-populated it with some data. This is done outside MW. 2. I then created a local extension (which implements a tag <Status>) to retrieve the data and displayed them as a html table. 3. I crated a page (XYZ) contains one statement -- <Status />. When I save the page, the table is displayed correctly. 4. There were some changes made to the table inside MySQL. When I follow a link to the XYZ page, I see the old contents of the page. 5. When I "edit" and "save" the XYZ page, then I see the updated data in the table.
My question: 1. Is there a way to skip the "edit" & "save" steps and see the updated data when I visit the XYZ page? 2. If I have no way to stop the "changing data value inside MySQL directly" behavior, how do I adapt MW to live with this condition?
Thanks to anybody for help in advance.
Nelson
Computer Sciences Corporation Registered Office: 2100 East Grand Avenue, El Segundo California 90245, USA Registered in USA No: C-489-59
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
On 19/12/2007, Nelson A Li nli@csc.com wrote:
Hello,
My problem:
- I created a table in my wikidb and pre-populated it with some data.
This is done outside MW. 2. I then created a local extension (which implements a tag <Status>) to retrieve the data and displayed them as a html table. 3. I crated a page (XYZ) contains one statement -- <Status />. When I save the page, the table is displayed correctly. 4. There were some changes made to the table inside MySQL. When I follow a link to the XYZ page, I see the old contents of the page. 5. When I "edit" and "save" the XYZ page, then I see the updated data in the table.
My question:
- Is there a way to skip the "edit" & "save" steps and see the updated
data when I visit the XYZ page? 2. If I have no way to stop the "changing data value inside MySQL directly" behavior, how do I adapt MW to live with this condition?
Thanks to anybody for help in advance.
You would have to do something when updating the database to tell MW that the cache is no longer valid. I'm sure it's doable, but I don't know how. A quick workaround would be to make an empty template and transclude it to all pages that use the <status> tag (which can probably be done automatically by the extension), and then you just have to make a null edit to the template, rather than every page, and it should automatically update all the other pages using the job queue. (I think that's how the cache works with templates, anyway... The MW cache has always confused me.)
Tom,
It sounds very interesting. However, you are talking to a php/MW apprentice here. Could you elaborate the following points?
1. to make an empty template and transclude it to all pages that use the <status> tag (which can probably be done automatically by the extension)
Do I create a template contains <Status /> and link to this template (eg. {{Template:status}} in XYZ page?
2. to make an empty template ... use the <status> tag (which can probably be done automatically by the extension)
Do you mean calling something inside the extension code?
3. then you just have to make a null edit to the template -- How to do null edit a template?
Nelson
Computer Sciences Corporation Registered Office: 2100 East Grand Avenue, El Segundo California 90245, USA Registered in USA No: C-489-59
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"Thomas Dalton" <thomas.dalton@gm ail.com> To Sent by: "MediaWiki announcements and site mediawiki-l-bounc admin list" es@lists.wikimedi mediawiki-l@lists.wikimedia.org a.org cc
Subject 12/19/2007 01:42 Re: [Mediawiki-l] Update page PM contents
Please respond to MediaWiki announcements and site admin list <mediawiki-l@list s.wikimedia.org>
On 19/12/2007, Nelson A Li nli@csc.com wrote:
Hello,
My problem:
- I created a table in my wikidb and pre-populated it with some data.
This is done outside MW. 2. I then created a local extension (which implements a tag <Status>)
to
retrieve the data and displayed them as a html table. 3. I crated a page (XYZ) contains one statement -- <Status />. When I save the page, the table is displayed correctly. 4. There were some changes made to the table inside MySQL. When I
follow
a link to the XYZ page, I see the old contents of the page. 5. When I "edit" and "save" the XYZ page, then I see the updated data
in
the table.
My question:
- Is there a way to skip the "edit" & "save" steps and see the updated
data when I visit the XYZ page? 2. If I have no way to stop the "changing data value inside MySQL directly" behavior, how do I adapt MW to live with this condition?
Thanks to anybody for help in advance.
You would have to do something when updating the database to tell MW that the cache is no longer valid. I'm sure it's doable, but I don't know how. A quick workaround would be to make an empty template and transclude it to all pages that use the <status> tag (which can probably be done automatically by the extension), and then you just have to make a null edit to the template, rather than every page, and it should automatically update all the other pages using the job queue. (I think that's how the cache works with templates, anyway... The MW cache has always confused me.)
_______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
On 19/12/2007, Nelson A Li nli@csc.com wrote:
Tom,
It sounds very interesting. However, you are talking to a php/MW apprentice here. Could you elaborate the following points?
- to make an empty template and transclude it to all pages that use the
<status> tag (which can probably be done automatically by the extension)
Do I create a template contains <Status /> and link to this template (eg. {{Template:status}} in XYZ page?
That wasn't what I had in mind, but it should work.
- to make an empty template ... use the <status> tag (which can probably
be done automatically by the extension)
Do you mean calling something inside the extension code?
The extension will contain a parser hook that replaces the tag with whatever you want, I was suggesting just adding {{status}} to the end of that output.
- then you just have to make a null edit to the template -- How to do
null edit a template?
Same way as with any other page - null edit just means clicking edit and immediately clicking save without changing anything. I foolishly assumed everyone knew mediawiki jargon... I should know better, sorry.
Good to learn. It seems the problem I encountered is a typical "null edit" situation. Sounds like there is no automatic "null edit" feature currently?
Nelson
Computer Sciences Corporation Registered Office: 2100 East Grand Avenue, El Segundo California 90245, USA Registered in USA No: C-489-59
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"Thomas Dalton" <thomas.dalton@gm ail.com> To Sent by: "MediaWiki announcements and site mediawiki-l-bounc admin list" es@lists.wikimedi mediawiki-l@lists.wikimedia.org a.org cc
Subject 12/19/2007 03:13 Re: [Mediawiki-l] Update page PM contents
Please respond to MediaWiki announcements and site admin list <mediawiki-l@list s.wikimedia.org>
On 19/12/2007, Nelson A Li nli@csc.com wrote:
Tom,
It sounds very interesting. However, you are talking to a php/MW apprentice here. Could you elaborate the following points?
- to make an empty template and transclude it to all pages that use the
<status> tag (which can probably be done automatically by the extension)
Do I create a template contains <Status /> and link to this template (eg. {{Template:status}} in XYZ page?
That wasn't what I had in mind, but it should work.
- to make an empty template ... use the <status> tag (which can probably
be done automatically by the extension)
Do you mean calling something inside the extension code?
The extension will contain a parser hook that replaces the tag with whatever you want, I was suggesting just adding {{status}} to the end of that output.
- then you just have to make a null edit to the template -- How to do
null edit a template?
Same way as with any other page - null edit just means clicking edit and immediately clicking save without changing anything. I foolishly assumed everyone knew mediawiki jargon... I should know better, sorry.
_______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
On 19/12/2007, Nelson A Li nli@csc.com wrote:
Good to learn. It seems the problem I encountered is a typical "null edit" situation. Sounds like there is no automatic "null edit" feature currently?
Some of the javascript tools floating around on Wikipedia have an option to do a null edit with one click, I think. Take a look at http://en.wikipedia.org/wiki/Wikipedia:WikiProject User scripts/Scripts for more info.
On 19/12/2007, Thomas Dalton thomas.dalton@gmail.com wrote:
On 19/12/2007, Nelson A Li nli@csc.com wrote:
Good to learn. It seems the problem I encountered is a typical "null edit" situation. Sounds like there is no automatic "null edit" feature currently?
Some of the javascript tools floating around on Wikipedia have an option to do a null edit with one click, I think. Take a look at http://en.wikipedia.org/wiki/Wikipedia:WikiProject User scripts/Scripts for more info.
Let me try that again...
http://en.wikipedia.org/wiki/Wikipedia:WikiProject_User_scripts/Scripts
Looking at some of the RSS reader extensions, there seem to be ways to disable the cache for specific pages containing extensions. For example, see:
http://www.mediawiki.org/wiki/Extension:RSS_Reader
Haven't tried this myself.
JH
On Dec 19, 2007, at 2:44 PM, Thomas Dalton wrote:
On 19/12/2007, Thomas Dalton thomas.dalton@gmail.com wrote:
On 19/12/2007, Nelson A Li nli@csc.com wrote:
Good to learn. It seems the problem I encountered is a typical "null edit" situation. Sounds like there is no automatic "null edit" feature currently?
Some of the javascript tools floating around on Wikipedia have an option to do a null edit with one click, I think. Take a look at http://en.wikipedia.org/wiki/Wikipedia:WikiProject User scripts/Scripts for more info.
Let me try that again...
http://en.wikipedia.org/wiki/Wikipedia:WikiProject_User_scripts/ Scripts
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
===================================== Jim Hu Associate Professor Dept. of Biochemistry and Biophysics 2128 TAMU Texas A&M Univ. College Station, TX 77843-2128 979-862-4054
On 19/12/2007, Jim Hu jimhu@tamu.edu wrote:
Looking at some of the RSS reader extensions, there seem to be ways to disable the cache for specific pages containing extensions. For example, see:
http://www.mediawiki.org/wiki/Extension:RSS_ReaderHaven't tried this myself.
Depending on how loaded the servers are expected to be and how often the status is going to be updated, disabling the cache entirely for those pages might be a bad move. If the status changes frequently, and the site isn't expected to be too busy, then it's worth considering.
mediawiki-l@lists.wikimedia.org