Thanks you so much, Ate and David! I wouldn't have created a wiki name with a space if I knew this issue. :p
Cheers, Woonsan On Thursday, March 13, 2014 6:15 PM, Ate Douma <a...@douma.nu> wrote: On 13-03-14 23:11, Ate Douma wrote: >> On 13-03-14 23:02, Ate Douma wrote: >>> On 13-03-14 22:56, David S Taylor wrote: >>>> Yes, I am an Admin. I added Woonsan to Admin Group, but he tells me he >>>> still can't edit the page, nor access the AdminGroup page. >>> In that case I suspect the Woonsan's wiki name might not match up. >>> I remember Woonsan had the same/similar problem with the Apache Commons >>> wiki... >>> >>> I just notice you added his name to the AdminGroup using [Woonsan Ko]. >>> I'm not sure, but AFAIK the security system requires a 'proper' wiki name, >>> meaning camelCase and no spaces in the name? >>> >> Never mind the above. It seems this should be possible: Woonsan's wiki name >> on >> the Apache Commons wiki also has an embedded space and there he can edit >> pages... > >I think I got it. Looking back at the commit history for the Commons wiki, I >see >sebb changing his wiki name like so: > >- * [Woonsan Ko] >+ * [[Woonsan Ko]] > >After this, Woonsan could edit the Commons wiki, so likely the same change is >needed for the Portals wiki. > >> >> Maybe you can ask s...@apache.org who setup his account there. >> >>> >>>> Maybe there is >>>> another place to configure this >>> >>> AFAIK these two pages, AdminGroup and ContributorsGroup, are the only >>> places to >>> configure this. >>> >>>> >>>> -- >>>> David S Taylor >>>> CEO, Bluesunrise >>>> 707 529-9194 >>>> da...@bluesunrise.com >>>> >>>> >>>> >>>> On Thu, Mar 13, 2014 at 2:06 PM, Ate Douma <a...@douma.nu> wrote: >>>> >>>>> David, I think you already are an admin on the Portals wiki, which you can >>>>> check by going to: https://wiki.apache.org/portals/AdminGroup >>>>> Non-admin users won't be able to access that page. >>>>> Through that page you can add more admin users if you wish by just adding >>>>> their wiki names. >>>>> >>>>> In addition, non-admin contributor users (e.g. normal users) can be >>>>> configured on https://wiki.apache.org/portals/ContributorsGroup. >>>>> Such users cannot delete pages or modify the contributors group. >>>>> >>>>> There is nobody configured on the ContributorsGroup page yet, which makes >>>>> me conclude you must be setup already as an admin. >>>>> >>>>> Ate >>>>> >>>>> >>>>> On 13-03-14 21:38, David S Taylor wrote: >>>>> >>>>>> Not having much luck. Tried this page >>>>>> >>>>>> http://wiki.apache.org/general/HowToBeWikiAdministrator >>>>>> >>>>>> Went out to /x1/www/wiki.apache.org, looked at the wiki README there, and >>>>>> it says >>>>>> >>>>>> THIS FILE IS OUTDATED. SORRY! STOP READING PLEASE... >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Mar 12, 2014 at 8:21 AM, Woonsan Ko <woon_...@yahoo.com> wrote: >>>>>> >>>>>> Thanks, David! >>>>>>> >>>>>>> >>>>>>> Still I cannot edit the wiki page: >>>>>>> - https://wiki.apache.org/portals/Applications/WebContentProposal >>>>>>> >>>>>>> I want to edit the tasks section for aligning and minor corrections. >>>>>>> >>>>>>> I think I was able to edit the wiki pages such as following in the past, >>>>>>> but not now. >>>>>>> >>>>>>> - https://wiki.apache.org/portals/Applications/Release_Process >>>>>>> >>>>>>> May I edit the pages? >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Woonsan >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Friday, March 7, 2014 6:08 PM, David S Taylor <da...@bluesunrise.com> >>>>>>> wrote: >>>>>>> >>>>>>> Woonsan, >>>>>>> >>>>>>>> >>>>>>>> Please review it and let me know if you have any further questions. >>>>>>>>> >>>>>>>> >>>>>>>> No issues, +1 >>>>>>>> >>>>>>>> Regarding the wiki page, is this what you wanted? >>>>>>>> >>>>>>>> https://wiki.apache.org/portals/Applications/WebContentProposal >>>>>>>> >>>>>>>> Its also linked on the Applications front page here: >>>>>>>> >>>>>>>> https://wiki.apache.org/portals/Applications >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> David S Taylor >>>>>>>> CEO, Bluesunrise >>>>>>>> 707 529-9194 >>>>>>>> da...@bluesunrise.com >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Mar 7, 2014 at 9:40 AM, Woonsan Ko <woon_...@yahoo.com> wrote: >>>>>>>> >>>>>>>> Hi Folks, >>>>>>>>> >>>>>>>>> I posted an idea to refactor apa-webcontent a while ago [1] and >>>>>>>>> promised >>>>>>>>> to write down a proposal/plan in a portals wiki page. I don't know >>>>>>>>> why, >>>>>>>>> >>>>>>>> but >>>>>>> >>>>>>>> I can't add a wiki page in >>>>>>>>> >>>>>>>> https://wiki.apache.org/portals/Applicationsat the moment. So, could >>>>>>> someone allow me to add a page there? (I'm getting >>>>>>> >>>>>>>> "You are not allowed to edit this page." when creating an empty page.) >>>>>>>>> >>>>>>>>> Anyway, I'm writing down a brief proposal including objectives, tasks >>>>>>>>> >>>>>>>> and >>>>>>> >>>>>>>> possible plans here. Please review it and let me know if you have any >>>>>>>>> further questions. (As soon as I get consensus on this, I'll try to >>>>>>>>> >>>>>>>> create >>>>>>> >>>>>>>> a wiki page and JIRA tickets to proceed.) >>>>>>>>> >>>>>>>>> ----- >>>>>>>>> >>>>>>>>> >>>>>>>>> Apache Portals Web Content Application 2.x Proposal >>>>>>>>> >>>>>>>>> 1. Objectives >>>>>>>>> - Reverse proxy module to be runnable in both portlet env and >>>>>>>>> servlet >>>>>>>>> (non-portlet) env >>>>>>>>> - Easier and more flexible content rewriting module >>>>>>>>> - More intuitive reverse proxy mapping configuration >>>>>>>>> - More componentized module structure and usage of an IoC >>>>>>>>>container >>>>>>>>> - More extensible SSO integration support >>>>>>>>> - Other possible extensibility (e.g, to support custom ESI >>>>>>>>> processing >>>>>>>>> component) >>>>>>>>> >>>>>>>>> 2. Assumptions >>>>>>>>> - 2.0 may break backward compatibility in both code and >>>>>>>>> configuration >>>>>>>>> >>>>>>>>> 3. Tasks >>>>>>>>> 3.1. Branching apa-webcontent-1.x and use trunk for 2.x. >>>>>>>>> 3.2. Maven project restructuring >>>>>>>>> - content-rewriter : content rewriting module decoupled with >>>>>>>>> portlet-api >>>>>>>>> - reverse-proxy : reverse proxy module decoupled with >>>>>>>>>portlet-api >>>>>>>>> - portlets : portlet classes >>>>>>>>> - war : (portlet) web application >>>>>>>>> 3.3. Change package name structure >>>>>>>>> (org.apache.portals.application.webcontent2.**) >>>>>>>>> 3.4. Componentizing reverse proxy module >>>>>>>>> - use spring framework or anything else as dependency injection? >>>>>>>>> 3.5. Improve reverse proxy mapping configuration >>>>>>>>> - consider using YAML instead of properties file >>>>>>>>> 3.6. Designing Content Rewriter module and evaluating 3rd party >>>>>>>>> solutions (e.g, htmlcleaner) >>>>>>>>> 3.7. Implementing Content Rewriter module with componentization >>>>>>>>> 3.8. Evaluating open (de facto) SSO standards/technologies to >>>>>>>>> possibly >>>>>>>>> integrate >>>>>>>>> 3.9. Provide external SSO integration API with an example >>>>>>>>> 3.10. Considering other possible >>>>>>>>> extensibility >>>>>>>>> >>>>>>>>> 4. Possible candidate plans >>>>>>>>> - 2.0 (Task 3.1 to 3.5) >>>>>>>>> - 2.1 (Task 3.6 to 3.7) >>>>>>>>> - 2.2 (Task 3.8 to 3.9) >>>>>>>>> - 2.3 (Task 3.10 ~ ) >>>>>>>>> >>>>>>>>> ----- >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Woonsan >>>>>>>>> >>>>>>>>> [1] http://web.archiveorange.com/archive/v/3HoJWKOPGLYhpCfybLG5 >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: jetspeed-dev-unsubscr...@portals.apache.org >>>>> For additional commands, e-mail: jetspeed-dev-h...@portals.apache.org > >>>>> >>>>> >>>> >>> >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: jetspeed-dev-unsubscr...@portals.apache.org >For additional commands, e-mail: jetspeed-dev-h...@portals.apache.org > > > >
