14 Mar
2008
14 Mar
'08
1:07 a.m.
Hi All,
I've changed my default skin to a custom skin. Once logged in all users on
all pages get this default theme.... :)
However, the login page has the albatross theme still. I've tried adding
&skin=myskin on the end and that works brilliant. But that's not good
behaviour.
What am I missing in order to fix this?
Thanks in Advance
--Andrew
15 Mar
15 Mar
2:13 a.m.
Andrew Hughes wrote:
Hi All,
I've changed my default skin to a custom skin. Once logged in all
users on all pages get this default theme.... :)
However, the login page has the albatross theme still. I've tried
adding &skin=myskin on the end and that works brilliant. But that's
not good behaviour.
What am I missing in order to fix this?
Have you set "Always authenticate on viewing:" to Yes?
HTH,
--
Ricardo Rodríguez
Your EPEC Network ICT Team
17 Mar
17 Mar
1:49 a.m.
Yes, it's most certainly set :'(
On Sat, Mar 15, 2008 at 11:43 AM, [Ricardo Rodriguez] Your EPEC Network ICT
Team <webmaster(a)environmentalchange.net> wrote:
Andrew Hughes wrote:
Hi All,
I've changed my default skin to a custom skin. Once logged in all
users on all pages get this default theme.... :)
However, the login page has the albatross theme still. I've tried
adding &skin=myskin on the end and that works brilliant. But that's
not good behaviour.
What am I missing in order to fix this?
Have you set "Always authenticate on viewing:" to Yes?
HTH,
--
Ricardo Rodríguez
Your EPEC Network ICT Team
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
18 Mar
18 Mar
12:28 a.m.
Hi,
Andrew Hughes wrote:
Yes, it's most certainly set :'(
I see
what you say (same behavior here), but I am afraid I've not the
solution. I don't know enough about XWiki structure as to help you with
this issue. Let's see if other can help.
In any case, I keep attentive to this thread.
Thanks!
--
Ricardo Rodríguez
Your EPEC Network ICT Team
19 Mar
19 Mar
7:20 a.m.
Thanks Ricardo,
Problem still persists...... anyone else have any ideas? Im getting a little
concerned.... I might just have to go rename my own skin albatross....
On Tue, Mar 18, 2008 at 9:58 AM, [Ricardo Rodriguez] Your EPEC Network ICT
Team <webmaster(a)environmentalchange.net> wrote:
Hi,
Andrew Hughes wrote:
Yes, it's most certainly set :'(
I see what you say (same behavior here), but I am afraid I've not the
solution. I don't know enough about XWiki structure as to help you with
this issue. Let's see if other can help.
In any case, I keep attentive to this thread.
Thanks!
--
Ricardo Rodríguez
Your EPEC Network ICT Team
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
10:58 a.m.
Andrew Hughes wrote:
Thanks Ricardo,
Problem still persists...... anyone else have any ideas? Im getting a
little concerned.... I might just have to go rename my own skin
albatross....
This must not be needed. I think twicking default albatross and/or
Toucan skins is by no means advisable... I've done this and having a lot
of problems afterwards. And it is quite difficult to decide later if the
problems comes from a modification in the default files or newly created
files.
I've found this in Jira... http://jira.xwiki.org/jira/browse/CHRONO-274
It seems that some kind of rights assignment could be related with what
we are seeing.
Perhaps some more information will help other to have a clearer idea
about this issue. And help us to open a Jira Issue about it.
1. What XWiki release are you using? Any product on top of it? What
installation (standalone, war)?
2. Have you modified xwiki.cfg skin related parameters? Here what do
they read by default:
xwiki.defaultskin=toucan
xwiki.defaultbaseskin=albatross
I am seeing the same behavior in some virtual wikis running on a XE 1.3
installation. Each virtual wiki has its customized skin but I have not
modified xwiki.cfg. Thus, any CSS or JS not found in the customized skin
folder is picked up from Albatross. But if I set Always authenticate on
viewing: to yes, Toucan is used to render the login page.
To see this solved will also help me!
Cheers,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
11:06 a.m.
Hi Andrew,
To check whether the problem is rights-related (it might be if the skin page
is stored in the wiki), go to your Skin page with an Admin account, click on
edit -> page access rights, and then tick the view right for Unregistered
users.
This will make only that specific page viewable (which does not matter much)
and might solve your problem.
If this trick solves the issue, it would mean you problem stemmed from the
fact that XWiki refused to display the contents of the page to users who
didn't have the rights to see it, therefore preventing your skin from being
parsed & used. I'm not sure that's it but it might be worth a shot :-)
Hope this will work,
Guillaume
On 19/03/2008, [Ricardo Rodriguez] Your EPEC Network ICT Team <
webmaster(a)environmentalchange.net> wrote:
Andrew Hughes wrote:
--
http://wikibc.blogspot.com/
Thanks Ricardo,
Problem still persists...... anyone else have any ideas? Im getting a
little concerned.... I might just have to go rename my own skin
albatross....
This must not be needed. I think twicking default albatross and/or
Toucan skins is by no means advisable... I've done this and having a lot
of problems afterwards. And it is quite difficult to decide later if the
problems comes from a modification in the default files or newly created
files.
I've found this in Jira... http://jira.xwiki.org/jira/browse/CHRONO-274
It seems that some kind of rights assignment could be related with what
we are seeing.
Perhaps some more information will help other to have a clearer idea
about this issue. And help us to open a Jira Issue about it.
1. What XWiki release are you using? Any product on top of it? What
installation (standalone, war)?
2. Have you modified xwiki.cfg skin related parameters? Here what do
they read by default:
xwiki.defaultskin=toucan
xwiki.defaultbaseskin=albatross
I am seeing the same behavior in some virtual wikis running on a XE 1.3
installation. Each virtual wiki has its customized skin but I have not
modified xwiki.cfg. Thus, any CSS or JS not found in the customized skin
folder is picked up from Albatross. But if I set Always authenticate on
viewing: to yes, Toucan is used to render the login page.
To see this solved will also help me!
Cheers,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
12:03 p.m.
Thanks Guillaume,
Guillaume Lerouge wrote:
Hi Andrew,
To check whether the problem is rights-related (it might be if the
skin page is stored in the wiki), go to your Skin page with an Admin
account, click on edit -> page access rights, and then tick the view
right for Unregistered users.
This will make only that specific page viewable (which does not matter
much) and might solve your problem.
If this trick solves the issue, it would mean you problem stemmed from
the fact that XWiki refused to display the contents of the page to
users who didn't have the rights to see it, therefore preventing your
skin from being parsed & used. I'm not sure that's it but it might be
worth a shot :-)
Hope this will work,
Guillaume
This doesn't work here at least. I've two customized skin, one being
used just for the home page and other for the rest of the site. In both
pages, Unregistered Users are granted View right. But if I set Always
authenticate on viewing: to yes, Toucan is used to render the login page.
Any other page implied in the process we must grant access to? Could I
be misinterpreting the steps you propose? Thanks!!!
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
4:37 p.m.
Hi,
Where did you define your custom skin?
My take is that because you have "always authenticate on viewing"
enabled, the skin document is inaccessible.
You can define your skin in xwiki.cfg, see xwiki.defaultskin
Andrew Hughes wrote:
Thanks Ricardo,
Problem still persists...... anyone else have any ideas? Im getting a
little concerned.... I might just have to go rename my own skin
albatross....
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
5 p.m.
Hi,
Sergiu Dumitriu wrote:
Hi,
Where did you define your custom skin?
My take is that because you have "always authenticate on viewing"
enabled, the skin document is inaccessible.
You can define your skin in xwiki.cfg, see xwiki.defaultskin
But this will affect to the main and virtual wikis, I guess. Is it
possible to have a customized skin applied to each xwiki login page?
Perhaps it could be possible to use the same method proposed by Guillaume...
http://code.xwiki.org/xwiki/bin/view/Snippets/ForceSkinSnippet
But I don't know how to do this with the login page yet. Any help will
be welcome! Thanks.
Cheers,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
20 Mar
20 Mar
1:12 a.m.
Hmmm this is crazy...
I tried setting...
xwiki.defaultskin=myskin
xwiki.defaultbaseskin=myskin
But it still shows albatross for some reason....
I tried symlinking albatross -> myskin on the filesystem, and it wouldn't
load any skin at all (indicates a permission problem, but not filesystem
permissions)
I did....
mv albatross albatross_orig; cp -Rp myskin albatross
and it works at the login page!
Guillaume, I can't edit the login page's access write's. If I login then try
to get to the login page, it fowards me to the wiki home page. So I can
never get to a position where I can change its access writes.
Never the less, I have a solution. Overwrite the albatross skin with
myskin... not the best... but the number of emails on this thread indicates
that it is not easy to replace in a clean fashion. I'm happy to call my skin
albaross if it means it saves me a day or so's worth of work.
Thanks for everyone that replied and tried to help!
On Thu, Mar 20, 2008 at 2:30 AM, [Ricardo Rodriguez] Your EPEC Network ICT
Team <webmaster(a)environmentalchange.net> wrote:
Hi,
Sergiu Dumitriu wrote:
Hi,
Where did you define your custom skin?
My take is that because you have "always authenticate on viewing"
enabled, the skin document is inaccessible.
You can define your skin in xwiki.cfg, see xwiki.defaultskin
But this will affect to the main and virtual wikis, I guess. Is it
possible to have a customized skin applied to each xwiki login page?
Perhaps it could be possible to use the same method proposed by
Guillaume...
http://code.xwiki.org/xwiki/bin/view/Snippets/ForceSkinSnippet
But I don't know how to do this with the login page yet. Any help will
be welcome! Thanks.
Cheers,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
1:24 a.m.
Hi Andrew,
Guillaume, I can't edit the login page's access write's. If I login then try
to get to the login page, it fowards me to the wiki
home page. So I can
never get to a position where I can change its access writes.
Before overwriting albatross, let's try this last step :
1. Go to http://<server>/xwiki/bin/edit/XWiki/XWikiLogin?editor=wiki
2. Add this code at the top of the page above any other content :
1. #if("$!request.skin" != "myskin")
$response.sendRedirect($doc.getURL("view", "skin=myskin")) #end
3. Click on Save & view
4. logout, then try to login again.
Hope this helps,
Guillaume
1:37 a.m.
Re,
Guillaume, I can't edit the login page's
access write's. If I login then
try to get to the login page, it fowards me to the wiki home page. So I can
never get to a position where I can change its access writes.
Before overwriting albatross, let's try this last step :
1. Go to http://<server>/xwiki/bin/edit/XWiki/XWikiLogin?editor=wiki
2. Add this code at the top of the page above any other content :
1. #if("$!request.skin" != "myskin")
$response.sendRedirect($doc.getURL("view", "skin=myskin"))
#end
3. Click on Save & view
4. logout, then try to login again.
Actually the solution I suggested doesn't work, but here's one that does :
Go to your xwiki folder on your filesystem -> go to webapps > xwiki >
templates & open login.vm in a text editor.
In the file, replace
#else
###
### Login page
###
###
with
#else
#if("$!request.skin" != "YOURSKINHERE")
$response.sendRedirect($doc.getURL("login", "skin=YOURSKINHERE"))
#end
###
### Login page
###
###
Save the file & try to login again -> you're done :-)
Guillaume
2:59 a.m.
Hi Guillaume.
Guillaume Lerouge wrote:
Go to your xwiki folder on your filesystem -> go to webapps > xwiki >
templates & open login.vm in a text editor.
In the file, replace
#else
###
### Login page
###
###
with
#else
#if("$!request.skin" != "YOURSKINHERE")
$response.sendRedirect($doc.getURL("login", "skin=YOURSKINHERE"))
#end
###
### Login page
###
###
Save the file & try to login again -> you're done :-)
Guillaume
Please, must I expect that this solutions works if I copy login.vm to a
new skin folder associated with a virtual wiki and modify it accordingly?
It works for me by modifying login.vm and forcing albatross instead of
toucan. But it doesn't work with a skin defined in a virtual wiki.
I guess Andrew doesn't user virtual wikis, so let's see if it works for him!
Thank you so much,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
26 Mar
26 Mar
12:12 a.m.
Thanks for this guys!!!!
I'm happy to give this a go, and I will do so. What I am wondering for the
greater community, is how this is reproducable over new versions of xwiki?
It seems that this is bound to the source vm. If I was to re-deploy xwiki
then I would drop this behaviour (I know this is the same with the skin
too).
Sorry if Im being a pain, but Im sure this is some functionality others
would like :)
...thanks & back soon!
On Thu, Mar 20, 2008 at 12:29 PM, [Ricardo Rodriguez] Your EPEC Network ICT
Team <webmaster(a)environmentalchange.net> wrote:
Hi Guillaume.
Guillaume Lerouge wrote:
Go to your xwiki folder on your filesystem -> go to webapps > xwiki >
templates & open login.vm in a text editor.
In the file, replace
#else
###
### Login page
###
###
with
#else
#if("$!request.skin" != "YOURSKINHERE")
$response.sendRedirect($doc.getURL("login", "skin=YOURSKINHERE"))
#end
###
### Login page
###
###
Save the file & try to login again -> you're done :-)
Guillaume
Please, must I expect that this solutions works if I copy login.vm to a
new skin folder associated with a virtual wiki and modify it accordingly?
It works for me by modifying login.vm and forcing albatross instead of
toucan. But it doesn't work with a skin defined in a virtual wiki.
I guess Andrew doesn't user virtual wikis, so let's see if it works for
him!
Thank you so much,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
1:18 p.m.
Hi Andrew,
Andrew Hughes-5 wrote:
Thanks for this guys!!!!
I'm happy to give this a go, and I will do so. What I am wondering for the
greater community, is how this is reproducable over new versions of xwiki?
It seems that this is bound to the source vm. If I was to re-deploy xwiki
then I would drop this behaviour (I know this is the same with the skin
too).
Sorry if Im being a pain, but Im sure this is some functionality others
would like :)
...thanks & back soon!
I know that a new Rendering/Parsing component/API is been actively developed
as many entries in devs list show, but I am not able to understand how this
will work yet.
As for working with 1.x releases, I think that there is no other way of
keeping customizations that keeping track of changes both in templates
stored in the general /templates folder and new skins' folders.
I have not been able yet to get this "customized skin applied to the login
page" issue solved here, so it will be great to have your feedback!
Cheers,
Ricardo
--
View this message in context:
http://www.nabble.com/Custom-Default-Skin-Everywhere%2C-Except-Login-Page-t…
Sent from the XWiki- Users mailing list archive at Nabble.com.
1:22 p.m.
On Mar 26, 2008, at 1:18 PM, [Ricardo Rodríguez] wrote:
Hi Andrew,
Andrew Hughes-5 wrote:
If you're interested to follow:
* http://dev.xwiki.org/xwiki/bin/view/Design/NewRenderingArchitecture
* http://svn.xwiki.org/svnroot/sandbox/components/xwiki-rendering/
Now what you're referring is probably the interface extension which is
different:
http://dev.xwiki.org/xwiki/bin/view/Design/InterfaceExtensions
-Vincent
Thanks for this guys!!!!
I'm happy to give this a go, and I will do so. What I am wondering
for the
greater community, is how this is reproducable over new versions of
xwiki?
It seems that this is bound to the source vm. If I was to re-deploy
xwiki
then I would drop this behaviour (I know this is the same with the
skin
too).
Sorry if Im being a pain, but Im sure this is some functionality
others
would like :)
...thanks & back soon!
I know that a new Rendering/Parsing component/API is been actively
developed
as many entries in devs list show, but I am not able to understand
how this
will work yet. As for working with 1.x releases, I think that there
is no other way
of
keeping customizations that keeping track of changes both in templates
stored in the general /templates folder and new skins' folders.
I have not been able yet to get this "customized skin applied to the
login
page" issue solved here, so it will be great to have your feedback!
Cheers,
Ricardo
9 Apr
9 Apr
8:55 a.m.
Andrew Hughes wrote:
Thanks for this guys!!!!
I'm happy to give this a go, and I will do so. What I am wondering for the
greater community, is how this is reproducable over new versions of xwiki?
It seems that this is bound to the source vm. If I was to re-deploy xwiki
then I would drop this behaviour (I know this is the same with the skin
too).
Sorry if Im being a pain, but Im sure this is some functionality others
would like :)
...thanks & back soon!
Just an update. Following an answer of Sergiu to other question (a
trivial one of mine, see "about layout and skins") I've seen that by
applying the skin you want to XWiki space in Administration > Space
Preferences forces it to show up at login time.
HTH,
Ricardo
--
Ricardo Rodríguez
Your EPEC Network ICT Team
6101
days inactive
6127
days old
17 comments
6 participants
participants (6)
-
[Ricardo Rodriguez] Your EPEC Network ICT Team -
[Ricardo Rodríguez]
-
Andrew Hughes -
Guillaume Lerouge -
Sergiu Dumitriu -
Vincent Massol