Additions:

Documentation:
~-""DbInfoActionInfo""
Supporting code:
~-AdvancedFormOpen
~-GenerateUniqueId
>>This is the development page for the DbInfo action.::c::
Just a little action that provides Admins an easy way to inspect the **structure** of the tables Wikka is using. (It's not a data browser!)
* @uses MakeId()
$idDbInfo = $this->makeId('div','dbinfo');
echo '<div id="'.$idDbInfo.'">'."\n";
====Supporting methods====
As can be seen (and is documented in the docblock) the new ##""DbInfo()""## action uses two methods that are themselves beta features - both of them documented already: [[AdvancedFormOpen FormOpen()]] (in its beta version!) and [[GenerateUniqueId makeId()]]. See the documentation pages for for each for necessary supporting code for the DbInfo action!
====Styling====

Deletions:

Documentation: ""DbInfoActionInfo"">>This is the development page for the DbInfo action.::c::
Just a little action that provides Admins an easy way to inspect the structure of the tables Wikka is using.
echo '<div id="dbinfo">'."\n";
===Styling===

Additions:

Not a real todo, but it could potentially be extended to prompt for a user/password combination for another database user; that might be handy for Admins taking care of several Wikis installed on the same server. Let us know if you'd be interested in such a feature.

Deletions:

Edited on 2005-07-17 22:46:10 by JavaWoman[adding styling and reference to AdvancedReferrersHandler]

Additions:

Documentation: ""DbInfoActionInfo"">>This is the development page for the DbInfo action.::c::
Although the PHP implementation of MySQL provides a few shortcuts with special functions, these don't support all information that we need. However, the MySQL **##SHOW##** command can reveal all we need to know, and it can be used with the PHP PHP:mysql_query function.
===Styling===
>>**see also:**
""<a href="AdvancedReferrersHandler#hn_7._cssrefmenu.css">refmenu.css</a>"" on AdvancedReferrersHandler
>>The forms the action display are accessible. Like those for the AdvancedReferrersHandler, they need corresponding styling. In fact the styling is the same, but since these are stillbeta features they have not been turned into a general "forms" styling yet (as will eventually have to happen to give all forms a constent look and feel). For now, the solution was to extend the extra stylesheet created for the AdvancedReferrersHandler; it looks as follows now: ::c::
**##css/refmenu.css##**
%%(css;1)/*
This stylesheet is for the referrers and blacklist handlers.
It will need to be integrated with the main stylesheet.

Deletions:

Documentation: DbInfoActionInfo.>>This is the development page for the DbInfo action.::c::
Although the PHP implementation of MySQL provides a few shortcuts with special functions, these don't support all information that we need. However, the ***##SHOW##*** MySQL command can reveal all we need to know, and it can be used with the PHP PHP:mysql_query function.

Deletions:

Additions:

Of course it's possible to use an external client like ""PhpMyAdmin"" or a desktop client but for a quick lookup it's handy to have that information available right inside Wikka.
Although the PHP implementation of MySQL provides a few shortcuts with special functions, these don't support all information that we need. However, the ***##SHOW##*** MySQL command can reveal all we need to know, and it can be used with the PHP PHP:mysql_query function.
Apart from that, it makes use of the configured Wikka database user; what this user can see, really depends on what permissions it has been given prior to installation of Wikka, so your mileage may vary.

Deletions:

Of course it's possible to use an external client like PhpMyAdmin or a desktop client. but for a quick lookup it's handy to have that information available right inside Wikka.
Although the PHP implementation of MySQL provides a few shortcuts with special functions, these don't support all information that we need. However, the ##SHOW## MySQL command can reveal all we need to know, and it can be used with the PHP PHP:mysql_query function.
Apart from that, it makes use of the configured Wikka database user; what this user can see, really depends on what permissions it has been given prior to installation of Wikak, so your mileage may vary.

Deletions:

=====xxxxx Action=====
Documentation: xxxxxActionInfo.>>This is the development page for the xxxxx action.::c::
//This page is a **template**. It belongs to CategoryTemplate (which contains more handy templates). To create an action development page, [[http://wikka.jsnx.com/ActionTemplate/clone clone this page]] to a page called **xxxxxAction** (where xxxxx is the (capitalized) name of the action), replace all occurrences of 'xxxxx' with the name of the action and replace this paragraph with the actual content.//