Hello guys,
Please, does anyone here already installed the FreeMind extension? It seems an easy installaton but when i upload the "file.mm", it doesnt find it, and i got the error *Error: Mind Map file file.mm not found.* I uploaded the file.mm from MediaWiki upload page, but looks like the file doesn't exist. I also added the "mm" as a valid extension on LocalSettings.php. There is almost no documentation about it, and i cant fix it, someone knows this issue?
Best Regards.
Stephan Gomes Higuti
Hi, I want to use numeric IDs for the user_name column in the users table. Im wondering how this will affect the display of that user's name on various pages and places (such as the URL for their page and their talk page, for the display of their name in the edit history for a page etc.).
I want to do this as part of a SSO (single sign on) system - where the common (unchanging) ID amongst the various systems is only a numeric ID.
Anyone know how using a numeric ID will affect the display of the user's name on MediaWiki and if it will have any other ramifications?
For example, on this history page:
http://wiki/index.php?title=CUSTOMNAMESPACE:Architect_Core_Resources&lim... I see the authors name listed. Can I make sure hte NAME displayed uses user's user_real_name instead if user_name ??
The reason I cannot test this is because I write directly to the DB and refresh the history page but it shows the original username (before I edited the DB table). I dont have cachinbg so Im not sure why my direct DB edits dont chnage the displkay of the history page.
-- Also, in our current DB I see entries for user_name that look 'like' this:
Userabc Lastdef (Userabc Lastdef) and Userabc Lastdef (8/8/2007 14:37)
Can someone explain the parenthesis - Im guessing its placed by MediaWiki because of a duplicate, but maybe its our custom Auth code that did that?
Mike
I don't think that is the best way to go about what you're trying to do.
Not sure what your exact requirements are, but i'd suggest adding a new table (or an extra row to the user table -- not sure how safe that is, I'll let someone else comment on that).
Something like: TABLE user_sso user_id INT - the user id from the user table user_sso INT - your sso ID
Anyone know how using a numeric ID will affect the display of the user's
name on MediaWiki and if it will have any other ramifications? The user_name field store's the accounts username. Changing that to a numeric ID will give all your accounts numbers for usernames.
Can I make sure hte NAME displayed uses user's user_real_name instead if
user_name ?? I doubt it. Even if you can, its probably not a good idea.
The reason I cannot test this is because I write directly to the DB and
refresh the history page but it shows the original username (before I edited the DB table).
[...] Im not sure why my direct DB edits dont chnage the displkay of the
history page.
This is because the revision table has an extra rev_user_text field that you need to change as well.
Directly editing the database should be avoided unless you know what you're doing.
I'm not quite sure what you're asking with your last question, however MediaWiki should not be altering the user_name field.
Hope some of this helps.
-- Chris
Thanks for the response. I appreciate some feedback.
Ill likely go with the extra users table (is this an OK thing in mediawiki extensions)? Do you know of any docs or an extension that adds a table - how does it know to update the SQL schema just once (or is that a part of the install instructions)? I would like to make it automatic so the extension checks for the table and installs if its not there (but running that on every (login) request sounds very inefficient).
Im directly altering the DB on my local dev server - so its OK.
I think what happens is that the edit history is maintained using the username at the time of the edit - so changing the username wont make a difference until I edit something as that user - OR I need to update the rev_user_text in the revision table (which is something I know nothing about so far).
Mike
On Jan 29, 2013, at 7:22 PM, Chris Grant wrote:
I don't think that is the best way to go about what you're trying to do.
Not sure what your exact requirements are, but i'd suggest adding a new table (or an extra row to the user table -- not sure how safe that is, I'll let someone else comment on that).
Something like: TABLE user_sso user_id INT - the user id from the user table user_sso INT - your sso ID
Anyone know how using a numeric ID will affect the display of the user's
name on MediaWiki and if it will have any other ramifications? The user_name field store's the accounts username. Changing that to a numeric ID will give all your accounts numbers for usernames.
Can I make sure hte NAME displayed uses user's user_real_name instead if
user_name ?? I doubt it. Even if you can, its probably not a good idea.
The reason I cannot test this is because I write directly to the DB and
refresh the history page but it shows the original username (before I edited the DB table).
[...] Im not sure why my direct DB edits dont chnage the displkay of the
history page.
This is because the revision table has an extra rev_user_text field that you need to change as well.
Directly editing the database should be avoided unless you know what you're doing.
I'm not quite sure what you're asking with your last question, however MediaWiki should not be altering the user_name field.
Hope some of this helps.
-- Chris _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
One question:
If I keep a sso table that maps a user_id to a row in the users table, I would update Mediawiki's user.user_email column if their email chnaged. Should I do this by a user function? Or can I just update the DB column - and more importantly, if I do just update the user column, should I call some special function so other parts of the system get a triggered update?
Mike
On Jan 29, 2013, at 7:22 PM, Chris Grant wrote:
I don't think that is the best way to go about what you're trying to do.
Not sure what your exact requirements are, but i'd suggest adding a new table (or an extra row to the user table -- not sure how safe that is, I'll let someone else comment on that).
Something like: TABLE user_sso user_id INT - the user id from the user table user_sso INT - your sso ID
Anyone know how using a numeric ID will affect the display of the user's
name on MediaWiki and if it will have any other ramifications? The user_name field store's the accounts username. Changing that to a numeric ID will give all your accounts numbers for usernames.
Can I make sure hte NAME displayed uses user's user_real_name instead if
user_name ?? I doubt it. Even if you can, its probably not a good idea.
The reason I cannot test this is because I write directly to the DB and
refresh the history page but it shows the original username (before I edited the DB table).
[...] Im not sure why my direct DB edits dont chnage the displkay of the
history page.
This is because the revision table has an extra rev_user_text field that you need to change as well.
Directly editing the database should be avoided unless you know what you're doing.
I'm not quite sure what you're asking with your last question, however MediaWiki should not be altering the user_name field.
Hope some of this helps.
-- Chris _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Is this possible with Mediawiki and some extensions:
For example, consider a user who prefers french content...types in this: www.host.com/page/Integration
-ideally the URL path for a given page stays the same (as displayed in the browser) - to avoid a redirect -system checks users preferred language (say by ACCEPT_LANGUAGE header) - in this case its 'fr' -wiki looks up french version of the given page, if it exists it displays that content -if the french doesnt exist, it displays the english content -user would type the page name appended with /fr to force-edit the french version (to create it) -skin would still use users language for localized content for the layout (non-media wiki parts like header, footer, side navigation menu etc.)
Similar BUT NOT THE SAME as the Extension:Multilang, Extension:LanguageSelector, Extension:Polyglot, Extension:AutoLanguage extensions I see out there.
Is this possible to "fight" the wiki in bringing up a default page when one does not exist (instead of the mediawiki built-in behavior to bring up the page allowing the user to create it).
Any ideas welcome!
Mike Papper
Am 01.02.2013 00:47 schrieb "Mike Papper" bodaro@gmail.com:
Is this possible with Mediawiki and some extensions:
For example, consider a user who prefers french content...types in this:
www.host.com/page/Integration
-ideally the URL path for a given page stays the same (as displayed in
the browser) - to avoid a redirect
-system checks users preferred language (say by ACCEPT_LANGUAGE header) -
in this case its 'fr'
-wiki looks up french version of the given page, if it exists it displays
that content
-if the french doesnt exist, it displays the english content -user would type the page name appended with /fr to force-edit the french
version (to create it)
-skin would still use users language for localized content for the layout
(non-media wiki parts like header, footer, side navigation menu etc.)
Similar BUT NOT THE SAME as the Extension:Multilang,
Extension:LanguageSelector, Extension:Polyglot, Extension:AutoLanguage extensions I see out there.
Is this possible to "fight" the wiki in bringing up a default page when
one does not exist (instead of the mediawiki built-in behavior to bring up the page allowing the user to create it).
Any ideas welcome!
Mike Papper
Extension:Translate should fullfill your needs mostly. It provides a fallback language and other things. However, as for the theme, that is mostly up to its author, as long as those parts are not put into the interface messages.
Thanks for the pointer.
I forgot to mention that Im running on Heroku and theres no permanent file storage and there may be multiple machines availabel to serve requests.
Do you know if that is something the Extension:Translate would have an issue with? I read that it wants you to define as cache directory, and I would assume that thats just temporary storage and a performance issue not going to stop it from working correctly if requests go to different servers.
Mike
On Jan 31, 2013, at 5:49 PM, Ingo Malchow wrote:
Am 01.02.2013 00:47 schrieb "Mike Papper" bodaro@gmail.com:
Is this possible with Mediawiki and some extensions:
For example, consider a user who prefers french content...types in this:
www.host.com/page/Integration
-ideally the URL path for a given page stays the same (as displayed in
the browser) - to avoid a redirect
-system checks users preferred language (say by ACCEPT_LANGUAGE header) -
in this case its 'fr'
-wiki looks up french version of the given page, if it exists it displays
that content
-if the french doesnt exist, it displays the english content -user would type the page name appended with /fr to force-edit the french
version (to create it)
-skin would still use users language for localized content for the layout
(non-media wiki parts like header, footer, side navigation menu etc.)
Similar BUT NOT THE SAME as the Extension:Multilang,
Extension:LanguageSelector, Extension:Polyglot, Extension:AutoLanguage extensions I see out there.
Is this possible to "fight" the wiki in bringing up a default page when
one does not exist (instead of the mediawiki built-in behavior to bring up the page allowing the user to create it).
Any ideas welcome!
Mike Papper
Extension:Translate should fullfill your needs mostly. It provides a fallback language and other things. However, as for the theme, that is mostly up to its author, as long as those parts are not put into the interface messages. _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
mediawiki-l@lists.wikimedia.org