DrNic;211117 Wrote: 
> About the wiki registration Erland - I must have got my wires crossed as
> I read into this section wrongly?:
> > > > 
> > When publishing/sharing a menu you have the following options
> > 
> > * You can choose to register, the advantage with this is.....> > 
> 
I see, some explanation is needed on the different registration
mechanisms:

1. 
You should be able to register from inside the SlimServer web
interface, for example by clicking the "Register" link from the Custom
Browse interface. This will not register on my actual wiki, it will
register you in a menu database on my site. By doing this you can use
the "Publish" links from inside the Custom Browse web interface to
publish your customized menus and make them available for other users.
If you don't want to share your menus with other, there is no reason to
register this way. This type of the registration is what the text you
shown refers to.

2.
You can register on my issue tracking system, although it isn't
actually needed. You can publish bugs/features here in the forum or
directly in my issue tracking system without registration.

3.
You can't register on my wiki. This registration is needed for editing
the wiki pages and at the moment I don't allow anyone else than me to
do that. But you can post messages in the "discussion" tabs on the wiki
without registering.


-- 
erland

Erland Isaksson
'My homepage' (http://erland.homeip.net) 'My download page'
(http://erland.homeip.net/download)
(Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse,
Custom Scan,  Custom Skip, Multi Library and RandomPlayList plugins'
(http://wiki.erland.homeip.net/index.php/Category:SlimServer))
------------------------------------------------------------------------
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=36224

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/plugins

Reply via email to