[jira] [Commented] (ROL-2121) Remove six sites no longer using Roller from Community page

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16560837#comment-16560837
 ] 

Glen Mazza commented on ROL-2121:
-

Hi David, it doesn't seem appropriate to suggest certain websites are using 
Roller when they aren't, and impolite to link companies and people to dead 
links, especially those who didn't ask to be put on this page to begin with.

For background:

1.) While I was on the team from 2012 thru mid-2015 I had updated the Powered 
by Roller[1] list for all Roller blogs as I found them by Googling or people 
disclosing them. We went from about 8 blogs to 54 blogs during my time on the 
project.[2]

2.) In mid-2015 I forked Roller and went my own way due to architectural 
disagreements, and stopped maintaining the Roller Powered By List.

3.) In August 2017 I revisted the Powered By List after two years separate from 
the project and identified 26 out of 54 blogs no longer using Roller -- either 
the sites were now returning 404's or they were clearly on Wordpress, Ghost, 
etc., so I removed them.[3] Someone on Roller then revoked my write access to 
the Wiki so I could no longer remove dead links or non-Roller blogs. (Fair 
enough, as I work on a competitor product today, and an accurate display of 
Roller's usage would benefit me, not just users evaluating Roller.)

4.) I revisited the list again this week, and found another six blogs either 
returning 404s or non-Roller blogs, bringing Roller down to 22 actives. No 
longer having Wiki write access, I created this PR for those six to be removed.

5.) With this PR, instead of removing the six, you reverted my 2017 change, 
going back to the original list of 54 blogs, 32 of which either are not using 
Roller or are dead links today. The disclaimer given "Past and present blogs 
that have been powered by Roller" can be incorrectly taken to mean that all the 
blogs are using Roller today, it's just that some blogs are "past" (archived, 
no longer being updated). "URLs that currently or at one time hosted Roller 
blogs" would be more accurate, but it still seems more appropriate to remove 
clearly non-Roller blogs as well as no longer hyperlink companies and people's 
names to dead URLs.

For any project, would-be adopters go to the Powered By page to see (1) how 
well the project is in use today (if few people are using it, people evaluate 
other projects), (2) see sample usages of the project to judge if the product 
fits their needs. Your offhand view is that it's cool to provide a 
trip-down-memory-lane list of which > 60% are no longer using Roller however 
can give the impression that the project is misrepresenting its usage in order 
to spur its adoption (we are much more capable of determining whether a site is 
using Roller than an average would-be adopter). Your option, I'm not on the 
team anymore, but I'd again recommend dropping down to just the 22 actives.

Regards,
Glen

cc   [~rubys] [~curcuru] [~chrismattmann]

[1] https://cwiki.apache.org/confluence/display/ROLLER/PoweredByRoller
[2] 
https://cwiki.apache.org/confluence/pages/viewpreviousversions.action?pageId=31821770
[3] 
[https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=31821770=49=48]

 

> Remove six sites no longer using Roller from Community page
> ---
>
> Key: ROL-2121
> URL: https://issues.apache.org/jira/browse/ROL-2121
> Project: Apache Roller
>  Issue Type: Task
>Reporter: Glen Mazza
>Assignee: Roller Unassigned
>Priority: Major
>
> Hi, on the Powered by Roller page 
> ([https://cwiki.apache.org/confluence/display/ROLLER/PoweredByRoller),] the 
> following six sites are no longer using Roller (returning 404's or directing 
> to non-Roller sites), they should be removed from the list:
> [Carleton University Library (Ottawa, 
> Canada)|https://blogs.library.carleton.ca/roller/themadgicalweb/], [DZone's 
> JRoller|http://www.jroller.com/], [USA B2C|http://www.usab2c.com/roller/], 
> [Viithiisys Technologies|http://www.viithiisys.com/blog], [Mabula 
> Haverkamp|http://www.bulapedia.nl/blog/Gerard/] and [Markus 
> Malkusch|http://markus.malkusch.de/blog/].
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ROL-2121) Remove six sites no longer using Roller from Community page

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-2121:

Priority: Major  (was: Trivial)

> Remove six sites no longer using Roller from Community page
> ---
>
> Key: ROL-2121
> URL: https://issues.apache.org/jira/browse/ROL-2121
> Project: Apache Roller
>  Issue Type: Task
>Reporter: Glen Mazza
>Assignee: Roller Unassigned
>Priority: Major
>
> Hi, on the Powered by Roller page 
> ([https://cwiki.apache.org/confluence/display/ROLLER/PoweredByRoller),] the 
> following six sites are no longer using Roller (returning 404's or directing 
> to non-Roller sites), they should be removed from the list:
> [Carleton University Library (Ottawa, 
> Canada)|https://blogs.library.carleton.ca/roller/themadgicalweb/], [DZone's 
> JRoller|http://www.jroller.com/], [USA B2C|http://www.usab2c.com/roller/], 
> [Viithiisys Technologies|http://www.viithiisys.com/blog], [Mabula 
> Haverkamp|http://www.bulapedia.nl/blog/Gerard/] and [Markus 
> Malkusch|http://markus.malkusch.de/blog/].
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ROL-2121) Remove six sites no longer using Roller from Community page

[Glen Mazza (JIRA)]

Glen Mazza created ROL-2121:
---

 Summary: Remove six sites no longer using Roller from Community 
page
 Key: ROL-2121
 URL: https://issues.apache.org/jira/browse/ROL-2121
 Project: Apache Roller
  Issue Type: Task
Reporter: Glen Mazza
Assignee: Roller Unassigned


Hi, on the Powered by Roller page 
([https://cwiki.apache.org/confluence/display/ROLLER/PoweredByRoller),] the 
following six sites are no longer using Roller (returning 404's or directing to 
non-Roller sites), they should be removed from the list:

[Carleton University Library (Ottawa, 
Canada)|https://blogs.library.carleton.ca/roller/themadgicalweb/], [DZone's 
JRoller|http://www.jroller.com/], [USA B2C|http://www.usab2c.com/roller/], 
[Viithiisys Technologies|http://www.viithiisys.com/blog], [Mabula 
Haverkamp|http://www.bulapedia.nl/blog/Gerard/] and [Markus 
Malkusch|http://markus.malkusch.de/blog/].

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ROL-1756) getMostCommentedWeblogs() doesn't return most commented weblogs unless called with limit = -1

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-1756:

Assignee: (was: Glen Mazza)

> getMostCommentedWeblogs() doesn't return most commented weblogs unless called 
> with limit = -1
> -
>
> Key: ROL-1756
> URL: https://issues.apache.org/jira/browse/ROL-1756
> Project: Apache Roller
>  Issue Type: Bug
>  Components: Data Model & JPA Backend
>Affects Versions: 4.0
> Environment: Doesn't look environment-specific.  Environment was:  
> Roller 4.0, MySQL 5.0, unknown Java version.
>Reporter: Anil Gangolli
>Priority: Minor
>
> This issue was originally reported by Guglielmo Carandente 
> 
> If you call getMostCommentedWeblogs() with a limit value other than -1, it 
> may not actually return the most commented weblogs.
> This  getMostCommentedWeblogs() method is exposed as part of the site model 
> and the call goes down to WeblogEntryManager.getMostCommentedWeblogEntries().
> The problem results because the query itself does not do any ordering on its 
> result set because (according to a comment near the query definition) of a 
> restriction in JPA QL, yet if you pass a limit value other than -1 the query 
> result set is limited to the specified size.  The ordering is then done by 
> sorting the results in the Java code within the method 
> WeblogEntryManager.getMostCommentedWeblogEntries().  So if you limit of the 
> result set, it may not contain the most commented entries.  You'll just end 
> up sorting the first n entries returned by the query where n is the value of 
> limit passed.
> To work around this bug, you can pass -1 for the length limit  and then limit 
> the number of results you actually display in your velocity template.  
> The performance of this workaround may not be acceptable if you have a large 
> number of blogs on the site.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ROL-2079) Executable Roller WAR/JAR

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14524362#comment-14524362
 ] 

Glen Mazza commented on ROL-2079:
-

I'm opposed to this.  It's not our job to supply and maintain servlet 
containers and embedded databases, that's the responsibility of the user, along 
with making sure that his servlet container and database is properly secured 
and patched for his operating system, java version, etc.  It's outside our 
scope.  The user can see our community page with the 50 or so Roller blogs 
hosted on it to get an idea of Roller's capabilities, that's sufficient.

JSPWiki made in my opinion the regrettable decision to fatten itself up with 
executable distributions that look cute but once done, nobody wants to maintain 
and it ends up driving prospective committers away when they look at the 
mountain of executables that need to be updated and maintained everytime the 
servlet container or JSPWiki needs updating.


 Executable Roller WAR/JAR
 -

 Key: ROL-2079
 URL: https://issues.apache.org/jira/browse/ROL-2079
 Project: Apache Roller
  Issue Type: Wish
Reporter: Kohei Nozaki
Assignee: Roller Unassigned
Priority: Trivial

 Recently I found that executable WAR that used in some Java based web 
 applications such as Jenkins is nice, and I think it's useful for someone who 
 is looking for give Roller a try.
 It's just an idea yet, but fortunately, Roller is portable and it can run 
 with embedded databases (e.g. Derby or HSQLDB) and embedded containers (e.g. 
 Jetty or Embedded Tomcat?), so I guess it's not hard to create a executable 
 WAR distribution.
 Are there any difficulty in realize this? I'd like to get any feedback.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ROL-2079) Executable Roller WAR/JAR

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14524375#comment-14524375
 ] 

Glen Mazza commented on ROL-2079:
-

BTW, Kohei, users can already quickly test Roller just by doing mvn jetty:run 
(https://cwiki.apache.org/confluence/display/ROLLER/How+to+build+Roller).  
People who do not know how to run Maven commands rarely are going to be 
knowledgeable enough to safely deploy Roller on a Java servlet container and 
keep it properly maintained, patched, etc. anyway.

 Executable Roller WAR/JAR
 -

 Key: ROL-2079
 URL: https://issues.apache.org/jira/browse/ROL-2079
 Project: Apache Roller
  Issue Type: Wish
Reporter: Kohei Nozaki
Assignee: Roller Unassigned
Priority: Trivial

 Recently I found that executable WAR that used in some Java based web 
 applications such as Jenkins is nice, and I think it's useful for someone who 
 is looking for give Roller a try.
 It's just an idea yet, but fortunately, Roller is portable and it can run 
 with embedded databases (e.g. Derby or HSQLDB) and embedded containers (e.g. 
 Jetty or Embedded Tomcat?), so I guess it's not hard to create a executable 
 WAR distribution.
 Are there any difficulty in realize this? I'd like to get any feedback.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ROL-2073) Move hard-coded date / timestamp formatting to ApplicationResources

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14524384#comment-14524384
 ] 

Glen Mazza commented on ROL-2073:
-

Hi Kohei, thanks for investigating this.  Yes, it would be nice to move the 
date formatters into the application.properties but probably not the words 
around it as people frequently change the Posted by  at  in category 
 sentence anyway to get it appearing as they like and by keeping the words 
away, date-only formatters in the app.properties can be used in more places.  I 
don't think we have to go overboard though on minor things because we do allow 
templates to be modified by the blogger.

 Move hard-coded date / timestamp formatting to ApplicationResources
 ---

 Key: ROL-2073
 URL: https://issues.apache.org/jira/browse/ROL-2073
 Project: Apache Roller
  Issue Type: Improvement
  Components: Themes and Macros
Affects Versions: 5.1.2
Reporter: Kohei Nozaki
Assignee: Roller Unassigned
Priority: Trivial
 Attachments: ROL-2073.patch


 There're some hard-coded date / timestamp formatting as follows:
 In {{_day.vm}} or {{day.vm}} of templates:
 {noformat}
 $utils.formatDate($day,  MMM dd, )
 $utils.formatDate($entry.pubTime, hh:mma MMM dd, )
 {noformat}
 In {{CalendarTag#doStartTag()}}:
 {noformat}
 // formatter Month-Year title of calendar
 SimpleDateFormat formatTitle = new SimpleDateFormat( , mLocale);
 {noformat}
 In Japanese locale, it produces following expressions:
 # 水曜日 4 22, 2015
 # Posted at 02:15午後 4 22, 2015 by kyle in Technology  |  投稿されたコメント [0]
 # 4月 2015
 They looks pretty weird to Japanese people. I think Japanese people prefer 
 following expressions instead:
 # 2015年4月22日 (水)
 # Posted at 2015年4月22日 午後 02:15 (this may better to move the fragment 
 entirely, not only the date, but it might be too much for default templates)
 # 2015年4月
 And I think these strange expressions may effect badly to first impression of 
 Japanese people who just installed Roller so give it a try. so I'd like to 
 move these expressions to ApplicationResources so that allow templates to 
 show locale specific expressions. any thoughts?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ROL-2063) NextLink appears in latest entry of permalink

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14504582#comment-14504582
 ] 

Glen Mazza commented on ROL-2063:
-

It would seem like fixing the data model, rather than adding confusing/hacky 
code, is the better solution.  If storing time to the hundredths of a second 
requires the data model to support thousandths of a second, go ahead and fix 
the data model.  Roller easily supports database upgrades, it has for years.  
Maintaining a buggy database model just to avoid making database changes 
doesn't help Roller's growth long-term, indeed it just speeds its obsolescence. 
 You might as well argue for keeping buggy code just to avoid making code 
changes.

With a data model upgrade it is not necessary to test every single database 
Roller supports (I normally just check between one and three: MySQL, Derby, and 
PostgreSQL).  We don't generally test MS SQL Server, DB2, and Oracle for 
example.  Instead you update the scripts with what seems most logical (where 
there is a 2, make it a 3 in the upgrade scripts.) and if a user discovers 
a syntax problem with our changes they'll contact us with a patch or an alert 
for us to get it fixed.

 NextLink appears in latest entry of permalink
 -

 Key: ROL-2063
 URL: https://issues.apache.org/jira/browse/ROL-2063
 Project: Apache Roller
  Issue Type: Bug
  Components: Data Model  JPA Backend
Affects Versions: 5.1.1
 Environment: PostgreSQL 9.3.4
Reporter: Kohei Nozaki
Assignee: Roller Unassigned
Priority: Minor
 Fix For: 5.1.2

 Attachments: ROL-2063.patch, ROL-2063_alternative.patch, 
 ROL-2063_refresh.patch, ROL-2063_truncate.patch, 
 ROL-2063_truncate_update1.patch, ROL-2063_update1.patch


 -With PostgreSQL-, NextLink shouldn't be appeared in latest entry of 
 permalink, but sometimes it appears as the link to latest entry itself.
 The cause is precision of the column WEBLOGENTRY.PUBTIME in PostgreSQL. it is 
 created with the type timestamp(2) with time zone as specified in 
 postgresql.properties. the problem occurs as follows.
 1. Someone posts an entry. following SQL was executed:
 2015-02-23 17:07:26 JST LOG:  execute unnamed: INSERT INTO weblogentry (id, 
 allowcomments, anchor, commentdays, content_src, content_type, creator, link, 
 locale, pinnedtomain, plugins, pubtime, righttoleft, search_description, 
 status, summary, text, title, updatetime, categoryid, websiteid) VALUES ($1, 
 $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18, 
 $19, $20, $21)
 2015-02-23 17:07:26 JST DETAIL:  parameters: $1 = 
 '71837e6f-735b-4c7e-b498-6b432accdcb2', $2 = 't', $3 = 'test', $4 = '0', $5 = 
 NULL, $6 = NULL, $7 = 'kyle', $8 = NULL, $9 = 'en_US', $10 = 'f', $11 = '', 
 $12 = '2015-02-23 17:07:26.548+09', $13 = 'f', $14 = '', $15 = 'PUBLISHED', 
 $16 = '', $17 = 'test', $18 = 'test', $19 = '2015-02-23 17:07:26.551+09', $20 
 = 'fb216817-f8ea-46ec-aad9-35d9f222cac4', $21 = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d'
 2. Someone visits the permalink of the entry just posted. 
 JPAWeblogEntryManager#getNextEntry() is invoked and following SQL was 
 executed and the query returns a row of current latest entry itself.
 2015-02-23 17:07:34 JST LOG:  execute unnamed: SELECT id AS a1, 
 allowcomments AS a2, anchor AS a3, commentdays AS a4, content_src AS a5, 
 content_type AS a6, creator AS a7, link AS a8, lo
 cale AS a9, pinnedtomain AS a10, plugins AS a11, pubtime AS a12, righttoleft 
 AS a13, search_description AS a14, status AS a15, summary AS a16, text AS 
 a17, title AS a18, updatetime AS a19,
  categoryid AS a20, websiteid AS a21 FROM weblogentry WHERE (((websiteid = 
 $1) AND (status = $2)) AND (pubtime  $3)) ORDER BY pubtime ASC LIMIT $4 
 OFFSET $5
 2015-02-23 17:07:34 JST DETAIL:  parameters: $1 = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d', $2 = 'PUBLISHED', $3 = '2015-02-23 
 17:07:26.548+09', $4 = '1', $5 = '0'
 It caused by the entry of PUBTIME is stored after rounded in the table as 
 follows:
 roller2=# select title, pubtime FROM weblogentry WHERE (((websiteid = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d') AND (status = 'PUBLISHED')) AND 
 (pubtime  '2015-02-23 17:07:26.548+09')) ORDER BY pubtime ASC LIMIT '1' 
 OFFSET '0';
  title |  pubtime  
 ---+---
  test  | 2015-02-23 17:07:26.55+09
 (1 row)
 Roller compared '2015-02-23 17:07:26.548+09' against '2015-02-23 
 17:07:26.55+09' and recognized current latest entry itself as next entry 
 while PUBTIME was rounded '.548' to '.55'. I don't know where Roller keeps 
 '2015-02-23 17:07:26.548+09' but I guess that it saved in caches in Roller or 
 EclipseLink because restarting of application server solves the problem 
 temporarily.
 To solve the problem, I 

[jira] [Comment Edited] (ROL-2063) NextLink appears in latest entry of permalink

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505866#comment-14505866
 ] 

Glen Mazza edited comment on ROL-2063 at 4/21/15 9:56 PM:
--

Hi Kohei, MySQL 5.6.x has been around since 2011 
(http://dev.mysql.com/doc/relnotes/mysql/5.6/en/) don't worry about or make 
code for older versions.  We can take 5.6.x as the minimum we support.


was (Author: gmazza):
Hi Kohei, MySQL 5.6.x has been around since 2011 
(http://dev.mysql.com/doc/relnotes/mysql/5.6/en/) don't worry about or code to 
older versions.  We can take 5.6.x as the minimum we support.

 NextLink appears in latest entry of permalink
 -

 Key: ROL-2063
 URL: https://issues.apache.org/jira/browse/ROL-2063
 Project: Apache Roller
  Issue Type: Bug
  Components: Data Model  JPA Backend
Affects Versions: 5.1.1
 Environment: PostgreSQL 9.3.4
Reporter: Kohei Nozaki
Assignee: Roller Unassigned
Priority: Minor
 Fix For: 5.1.2

 Attachments: ROL-2063.patch, ROL-2063_alternative.patch, 
 ROL-2063_refresh.patch, ROL-2063_truncate.patch, 
 ROL-2063_truncate_update1.patch, ROL-2063_update1.patch


 -With PostgreSQL-, NextLink shouldn't be appeared in latest entry of 
 permalink, but sometimes it appears as the link to latest entry itself.
 The cause is precision of the column WEBLOGENTRY.PUBTIME in PostgreSQL. it is 
 created with the type timestamp(2) with time zone as specified in 
 postgresql.properties. the problem occurs as follows.
 1. Someone posts an entry. following SQL was executed:
 2015-02-23 17:07:26 JST LOG:  execute unnamed: INSERT INTO weblogentry (id, 
 allowcomments, anchor, commentdays, content_src, content_type, creator, link, 
 locale, pinnedtomain, plugins, pubtime, righttoleft, search_description, 
 status, summary, text, title, updatetime, categoryid, websiteid) VALUES ($1, 
 $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18, 
 $19, $20, $21)
 2015-02-23 17:07:26 JST DETAIL:  parameters: $1 = 
 '71837e6f-735b-4c7e-b498-6b432accdcb2', $2 = 't', $3 = 'test', $4 = '0', $5 = 
 NULL, $6 = NULL, $7 = 'kyle', $8 = NULL, $9 = 'en_US', $10 = 'f', $11 = '', 
 $12 = '2015-02-23 17:07:26.548+09', $13 = 'f', $14 = '', $15 = 'PUBLISHED', 
 $16 = '', $17 = 'test', $18 = 'test', $19 = '2015-02-23 17:07:26.551+09', $20 
 = 'fb216817-f8ea-46ec-aad9-35d9f222cac4', $21 = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d'
 2. Someone visits the permalink of the entry just posted. 
 JPAWeblogEntryManager#getNextEntry() is invoked and following SQL was 
 executed and the query returns a row of current latest entry itself.
 2015-02-23 17:07:34 JST LOG:  execute unnamed: SELECT id AS a1, 
 allowcomments AS a2, anchor AS a3, commentdays AS a4, content_src AS a5, 
 content_type AS a6, creator AS a7, link AS a8, lo
 cale AS a9, pinnedtomain AS a10, plugins AS a11, pubtime AS a12, righttoleft 
 AS a13, search_description AS a14, status AS a15, summary AS a16, text AS 
 a17, title AS a18, updatetime AS a19,
  categoryid AS a20, websiteid AS a21 FROM weblogentry WHERE (((websiteid = 
 $1) AND (status = $2)) AND (pubtime  $3)) ORDER BY pubtime ASC LIMIT $4 
 OFFSET $5
 2015-02-23 17:07:34 JST DETAIL:  parameters: $1 = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d', $2 = 'PUBLISHED', $3 = '2015-02-23 
 17:07:26.548+09', $4 = '1', $5 = '0'
 It caused by the entry of PUBTIME is stored after rounded in the table as 
 follows:
 roller2=# select title, pubtime FROM weblogentry WHERE (((websiteid = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d') AND (status = 'PUBLISHED')) AND 
 (pubtime  '2015-02-23 17:07:26.548+09')) ORDER BY pubtime ASC LIMIT '1' 
 OFFSET '0';
  title |  pubtime  
 ---+---
  test  | 2015-02-23 17:07:26.55+09
 (1 row)
 Roller compared '2015-02-23 17:07:26.548+09' against '2015-02-23 
 17:07:26.55+09' and recognized current latest entry itself as next entry 
 while PUBTIME was rounded '.548' to '.55'. I don't know where Roller keeps 
 '2015-02-23 17:07:26.548+09' but I guess that it saved in caches in Roller or 
 EclipseLink because restarting of application server solves the problem 
 temporarily.
 To solve the problem, I think changing precision of TIMESTAMP_SQL_TYPE_NULL 
 and TIMESTAMP_SQL_TYPE in /resources/sql/postgresql.properties from 2 to 3 is 
 reasonable because Roller uses milliseconds precision with java.util.Date, 
 larger precision is unnecessary though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ROL-2063) NextLink appears in latest entry of permalink

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505866#comment-14505866
 ] 

Glen Mazza commented on ROL-2063:
-

Hi Kohei, MySQL 5.6.x has been around since 2011 
(http://dev.mysql.com/doc/relnotes/mysql/5.6/en/) don't worry about or code to 
older versions.  We can take 5.6.x as the minimum we support.

 NextLink appears in latest entry of permalink
 -

 Key: ROL-2063
 URL: https://issues.apache.org/jira/browse/ROL-2063
 Project: Apache Roller
  Issue Type: Bug
  Components: Data Model  JPA Backend
Affects Versions: 5.1.1
 Environment: PostgreSQL 9.3.4
Reporter: Kohei Nozaki
Assignee: Roller Unassigned
Priority: Minor
 Fix For: 5.1.2

 Attachments: ROL-2063.patch, ROL-2063_alternative.patch, 
 ROL-2063_refresh.patch, ROL-2063_truncate.patch, 
 ROL-2063_truncate_update1.patch, ROL-2063_update1.patch


 -With PostgreSQL-, NextLink shouldn't be appeared in latest entry of 
 permalink, but sometimes it appears as the link to latest entry itself.
 The cause is precision of the column WEBLOGENTRY.PUBTIME in PostgreSQL. it is 
 created with the type timestamp(2) with time zone as specified in 
 postgresql.properties. the problem occurs as follows.
 1. Someone posts an entry. following SQL was executed:
 2015-02-23 17:07:26 JST LOG:  execute unnamed: INSERT INTO weblogentry (id, 
 allowcomments, anchor, commentdays, content_src, content_type, creator, link, 
 locale, pinnedtomain, plugins, pubtime, righttoleft, search_description, 
 status, summary, text, title, updatetime, categoryid, websiteid) VALUES ($1, 
 $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18, 
 $19, $20, $21)
 2015-02-23 17:07:26 JST DETAIL:  parameters: $1 = 
 '71837e6f-735b-4c7e-b498-6b432accdcb2', $2 = 't', $3 = 'test', $4 = '0', $5 = 
 NULL, $6 = NULL, $7 = 'kyle', $8 = NULL, $9 = 'en_US', $10 = 'f', $11 = '', 
 $12 = '2015-02-23 17:07:26.548+09', $13 = 'f', $14 = '', $15 = 'PUBLISHED', 
 $16 = '', $17 = 'test', $18 = 'test', $19 = '2015-02-23 17:07:26.551+09', $20 
 = 'fb216817-f8ea-46ec-aad9-35d9f222cac4', $21 = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d'
 2. Someone visits the permalink of the entry just posted. 
 JPAWeblogEntryManager#getNextEntry() is invoked and following SQL was 
 executed and the query returns a row of current latest entry itself.
 2015-02-23 17:07:34 JST LOG:  execute unnamed: SELECT id AS a1, 
 allowcomments AS a2, anchor AS a3, commentdays AS a4, content_src AS a5, 
 content_type AS a6, creator AS a7, link AS a8, lo
 cale AS a9, pinnedtomain AS a10, plugins AS a11, pubtime AS a12, righttoleft 
 AS a13, search_description AS a14, status AS a15, summary AS a16, text AS 
 a17, title AS a18, updatetime AS a19,
  categoryid AS a20, websiteid AS a21 FROM weblogentry WHERE (((websiteid = 
 $1) AND (status = $2)) AND (pubtime  $3)) ORDER BY pubtime ASC LIMIT $4 
 OFFSET $5
 2015-02-23 17:07:34 JST DETAIL:  parameters: $1 = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d', $2 = 'PUBLISHED', $3 = '2015-02-23 
 17:07:26.548+09', $4 = '1', $5 = '0'
 It caused by the entry of PUBTIME is stored after rounded in the table as 
 follows:
 roller2=# select title, pubtime FROM weblogentry WHERE (((websiteid = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d') AND (status = 'PUBLISHED')) AND 
 (pubtime  '2015-02-23 17:07:26.548+09')) ORDER BY pubtime ASC LIMIT '1' 
 OFFSET '0';
  title |  pubtime  
 ---+---
  test  | 2015-02-23 17:07:26.55+09
 (1 row)
 Roller compared '2015-02-23 17:07:26.548+09' against '2015-02-23 
 17:07:26.55+09' and recognized current latest entry itself as next entry 
 while PUBTIME was rounded '.548' to '.55'. I don't know where Roller keeps 
 '2015-02-23 17:07:26.548+09' but I guess that it saved in caches in Roller or 
 EclipseLink because restarting of application server solves the problem 
 temporarily.
 To solve the problem, I think changing precision of TIMESTAMP_SQL_TYPE_NULL 
 and TIMESTAMP_SQL_TYPE in /resources/sql/postgresql.properties from 2 to 3 is 
 reasonable because Roller uses milliseconds precision with java.util.Date, 
 larger precision is unnecessary though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ROL-2063) NextLink appears in latest entry of permalink

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14351903#comment-14351903
 ] 

Glen Mazza commented on ROL-2063:
-

If rounding the blog entry posting to the nearest second (or tenth of a second) 
would be doable, I think that is also a fine solution.  Basically, the time 
that we store should have less precision that what we have coded that database 
to accept (i.e., if we allow up to hundreths of a second we should be storing 
no more precise than tenths of a second.)  If I understand correctly, this 
problem is occurring because we're saving with a precision of thousandths of a 
second in databases that we've configured to just accept hundreths.

 NextLink appears in latest entry of permalink
 -

 Key: ROL-2063
 URL: https://issues.apache.org/jira/browse/ROL-2063
 Project: Apache Roller
  Issue Type: Bug
  Components: Data Model  JPA Backend
Affects Versions: 5.1.1
 Environment: PostgreSQL 9.3.4
Reporter: Kohei Nozaki
Assignee: David Johnson
Priority: Minor
 Fix For: 5.1.2

 Attachments: ROL-2063.patch, ROL-2063_alternative.patch, 
 ROL-2063_update1.patch


 -With PostgreSQL-, NextLink shouldn't be appeared in latest entry of 
 permalink, but sometimes it appears as the link to latest entry itself.
 The cause is precision of the column WEBLOGENTRY.PUBTIME in PostgreSQL. it is 
 created with the type timestamp(2) with time zone as specified in 
 postgresql.properties. the problem occurs as follows.
 1. Someone posts an entry. following SQL was executed:
 2015-02-23 17:07:26 JST LOG:  execute unnamed: INSERT INTO weblogentry (id, 
 allowcomments, anchor, commentdays, content_src, content_type, creator, link, 
 locale, pinnedtomain, plugins, pubtime, righttoleft, search_description, 
 status, summary, text, title, updatetime, categoryid, websiteid) VALUES ($1, 
 $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18, 
 $19, $20, $21)
 2015-02-23 17:07:26 JST DETAIL:  parameters: $1 = 
 '71837e6f-735b-4c7e-b498-6b432accdcb2', $2 = 't', $3 = 'test', $4 = '0', $5 = 
 NULL, $6 = NULL, $7 = 'kyle', $8 = NULL, $9 = 'en_US', $10 = 'f', $11 = '', 
 $12 = '2015-02-23 17:07:26.548+09', $13 = 'f', $14 = '', $15 = 'PUBLISHED', 
 $16 = '', $17 = 'test', $18 = 'test', $19 = '2015-02-23 17:07:26.551+09', $20 
 = 'fb216817-f8ea-46ec-aad9-35d9f222cac4', $21 = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d'
 2. Someone visits the permalink of the entry just posted. 
 JPAWeblogEntryManager#getNextEntry() is invoked and following SQL was 
 executed and the query returns a row of current latest entry itself.
 2015-02-23 17:07:34 JST LOG:  execute unnamed: SELECT id AS a1, 
 allowcomments AS a2, anchor AS a3, commentdays AS a4, content_src AS a5, 
 content_type AS a6, creator AS a7, link AS a8, lo
 cale AS a9, pinnedtomain AS a10, plugins AS a11, pubtime AS a12, righttoleft 
 AS a13, search_description AS a14, status AS a15, summary AS a16, text AS 
 a17, title AS a18, updatetime AS a19,
  categoryid AS a20, websiteid AS a21 FROM weblogentry WHERE (((websiteid = 
 $1) AND (status = $2)) AND (pubtime  $3)) ORDER BY pubtime ASC LIMIT $4 
 OFFSET $5
 2015-02-23 17:07:34 JST DETAIL:  parameters: $1 = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d', $2 = 'PUBLISHED', $3 = '2015-02-23 
 17:07:26.548+09', $4 = '1', $5 = '0'
 It caused by the entry of PUBTIME is stored after rounded in the table as 
 follows:
 roller2=# select title, pubtime FROM weblogentry WHERE (((websiteid = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d') AND (status = 'PUBLISHED')) AND 
 (pubtime  '2015-02-23 17:07:26.548+09')) ORDER BY pubtime ASC LIMIT '1' 
 OFFSET '0';
  title |  pubtime  
 ---+---
  test  | 2015-02-23 17:07:26.55+09
 (1 row)
 Roller compared '2015-02-23 17:07:26.548+09' against '2015-02-23 
 17:07:26.55+09' and recognized current latest entry itself as next entry 
 while PUBTIME was rounded '.548' to '.55'. I don't know where Roller keeps 
 '2015-02-23 17:07:26.548+09' but I guess that it saved in caches in Roller or 
 EclipseLink because restarting of application server solves the problem 
 temporarily.
 To solve the problem, I think changing precision of TIMESTAMP_SQL_TYPE_NULL 
 and TIMESTAMP_SQL_TYPE in /resources/sql/postgresql.properties from 2 to 3 is 
 reasonable because Roller uses milliseconds precision with java.util.Date, 
 larger precision is unnecessary though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ROL-2066) Comment URLs using https:// not saving properly in Gaurav theme

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-2066:

Summary: Comment URLs using https:// not saving properly in Gaurav theme  
(was: Commentors can't leave a comment using URL begins with https:// in Gaurav 
theme)

 Comment URLs using https:// not saving properly in Gaurav theme
 ---

 Key: ROL-2066
 URL: https://issues.apache.org/jira/browse/ROL-2066
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Affects Versions: 5.1.1
Reporter: Kohei Nozaki
Assignee: David Johnson
Priority: Trivial
 Fix For: 5.1.2

 Attachments: ROL-2066.patch, Screen Shot 2015-02-28 at 12.52.03.png, 
 Screen Shot 2015-02-28 at 12.52.17.png


 entry.vm in Gaurav theme has a convenient JavaScript method which named 
 fixURL(). it's binded in the onsubmit event handler in comment form and it 
 prepends http:// to commentor's URL if one has no scheme in the URL. for 
 example it converts the URL which a commentor entered as follows:
 {noformat}
 www.example.com = http://www.example.com
 {noformat}
 The code of the method is following:
 {code}
 function fixURL(theForm) {
 if (theForm.url.value !=  
 theForm.url.value.indexOf(http://;) == -1) { //prepend http://
 theForm.url.value = http://+theForm.url.value;
 }
 saveUserInformation(theForm);
 }
 {code}
 It works well for most cases, but not for a URL which begins with https:// or 
 some other schemes (e.g. ftp://). it goes wrong with such URL as follows:
 {noformat}
 https://www.example.com = http://https://www.example.com
 {noformat}
 I think current implementation of fixURL() which is simply searching 
 http://; is not enough.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ROL-2063) NextLink appears in latest entry of permalink

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349870#comment-14349870
 ] 

Glen Mazza commented on ROL-2063:
-

Kohei, I'm not sure what the problem you mention is.  Are you saying with 
PostgreSQL, for example, for this blog page:
https://web-gmazza.rhcloud.com/blog/entry/using-mtom-and-apache-fop

(1) the next link at the top which says Using UsernameToken... instead will 
say Returning PDFs From Web Services... (i.e., point to the same article as 
the URL)?
or 
(2) it will still say Using UsernameToken..., it's just that it will point to 
the Returning PDFs From Web Services article?
or 
(3) neither, the problem is for the date-based URLs such as this one:  
https://web-gmazza.rhcloud.com/blog/date/20141006. 

As for your alternative patch, only a small percentage post blog entries via 
BloggerAPIHandler or MetaWeblogAPIHandler.  I don't know if we'd want the more 
generic approach if it causes performance degradation for all if it is just for 
these APIs, it may be better to just expand the timestamp width for the 
databases for which this is an issue, something we can tell users to do 
themselves if they use the third party APIs and are having this problem.  I 
would say your current patch fixes the problem 90%, maybe we can keep this 
issue open for a post-5.1.2 release to fix the problem 100%.

 NextLink appears in latest entry of permalink
 -

 Key: ROL-2063
 URL: https://issues.apache.org/jira/browse/ROL-2063
 Project: Apache Roller
  Issue Type: Bug
  Components: Data Model  JPA Backend
Affects Versions: 5.1.1
 Environment: PostgreSQL 9.3.4
Reporter: Kohei Nozaki
Assignee: David Johnson
Priority: Minor
 Fix For: 5.1.2

 Attachments: ROL-2063.patch, ROL-2063_alternative.patch, 
 ROL-2063_update1.patch


 With PostgreSQL, NextLink shouldn't be appeared in latest entry of permalink, 
 but sometimes it appears as the link to latest entry itself.
 The cause is precision of the column WEBLOGENTRY.PUBTIME in PostgreSQL. it is 
 created with the type timestamp(2) with time zone as specified in 
 postgresql.properties. the problem occurs as follows.
 1. Someone posts an entry. following SQL was executed:
 2015-02-23 17:07:26 JST LOG:  execute unnamed: INSERT INTO weblogentry (id, 
 allowcomments, anchor, commentdays, content_src, content_type, creator, link, 
 locale, pinnedtomain, plugins, pubtime, righttoleft, search_description, 
 status, summary, text, title, updatetime, categoryid, websiteid) VALUES ($1, 
 $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18, 
 $19, $20, $21)
 2015-02-23 17:07:26 JST DETAIL:  parameters: $1 = 
 '71837e6f-735b-4c7e-b498-6b432accdcb2', $2 = 't', $3 = 'test', $4 = '0', $5 = 
 NULL, $6 = NULL, $7 = 'kyle', $8 = NULL, $9 = 'en_US', $10 = 'f', $11 = '', 
 $12 = '2015-02-23 17:07:26.548+09', $13 = 'f', $14 = '', $15 = 'PUBLISHED', 
 $16 = '', $17 = 'test', $18 = 'test', $19 = '2015-02-23 17:07:26.551+09', $20 
 = 'fb216817-f8ea-46ec-aad9-35d9f222cac4', $21 = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d'
 2. Someone visits the permalink of the entry just posted. 
 JPAWeblogEntryManager#getNextEntry() is invoked and following SQL was 
 executed and the query returns a row of current latest entry itself.
 2015-02-23 17:07:34 JST LOG:  execute unnamed: SELECT id AS a1, 
 allowcomments AS a2, anchor AS a3, commentdays AS a4, content_src AS a5, 
 content_type AS a6, creator AS a7, link AS a8, lo
 cale AS a9, pinnedtomain AS a10, plugins AS a11, pubtime AS a12, righttoleft 
 AS a13, search_description AS a14, status AS a15, summary AS a16, text AS 
 a17, title AS a18, updatetime AS a19,
  categoryid AS a20, websiteid AS a21 FROM weblogentry WHERE (((websiteid = 
 $1) AND (status = $2)) AND (pubtime  $3)) ORDER BY pubtime ASC LIMIT $4 
 OFFSET $5
 2015-02-23 17:07:34 JST DETAIL:  parameters: $1 = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d', $2 = 'PUBLISHED', $3 = '2015-02-23 
 17:07:26.548+09', $4 = '1', $5 = '0'
 It caused by the entry of PUBTIME is stored after rounded in the table as 
 follows:
 roller2=# select title, pubtime FROM weblogentry WHERE (((websiteid = 
 '78d076b8-19c2-4ee0-a766-2cdaf0b75d0d') AND (status = 'PUBLISHED')) AND 
 (pubtime  '2015-02-23 17:07:26.548+09')) ORDER BY pubtime ASC LIMIT '1' 
 OFFSET '0';
  title |  pubtime  
 ---+---
  test  | 2015-02-23 17:07:26.55+09
 (1 row)
 Roller compared '2015-02-23 17:07:26.548+09' against '2015-02-23 
 17:07:26.55+09' and recognized current latest entry itself as next entry 
 while PUBTIME was rounded '.548' to '.55'. I don't know where Roller keeps 
 '2015-02-23 17:07:26.548+09' but I guess that it saved in caches in Roller or 
 EclipseLink because restarting of 

[jira] [Updated] (ROL-2064) Add viewport meta tag to Gaurav theme

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-2064:

Summary: Add viewport meta tag to Gaurav theme  (was: Setting viewport to 
Gaurav theme)

 Add viewport meta tag to Gaurav theme
 -

 Key: ROL-2064
 URL: https://issues.apache.org/jira/browse/ROL-2064
 Project: Apache Roller
  Issue Type: Improvement
  Components: Themes and Macros
Affects Versions: 5.1.1
 Environment: Safari on iOS
Reporter: Kohei Nozaki
Assignee: David Johnson
Priority: Trivial
 Fix For: 5.1.2

 Attachments: ROL-2064.patch, after.png, before.png


 Gaurav is responsive but looks like missing viewport configuration. it's not 
 comfortable for smartphones. I guess adding viewport to std_head.vm is 
 reasonable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-1818) Testing login with https switched on

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1818.
---
Resolution: Cannot Reproduce

Greg noted today on the mailing list he hasn't seen this error for ages now.  
I believe I was talking about something else in my comment, if it occurs to me 
again I'll create a new issue with something reproducible.

 Testing login with https switched on
 

 Key: ROL-1818
 URL: https://issues.apache.org/jira/browse/ROL-1818
 Project: Apache Roller
  Issue Type: Test
  Components: User Interface - General
Affects Versions: 5.0
Reporter: Greg Huber
Assignee: Greg Huber
Priority: Minor

 Hello, 
 I have noticed that on the login when https is swithed on and every now and 
 then we get a access denied page after logging on, thrown from the 
 UISecurityInterceptor:
  User authenticatedUser = ((UIAction)theAction).getAuthenticatedUser();
  if(authenticatedUser == null) {
 log.debug(DENIED: required user not found);
  return access-denied;
   } 
 because the getAuthenticatedUser(); is null, and tracing this back the 
 request.getUserPrincipal(); from the rollersession is null.
 It seems to be something when the session is swithed over from https back to 
 http, as it does not happen when the https is off.
 I have tried to do some debugging but have not been able to pin point where 
 it goes wrong as its not consistant.  Also if the session times out (tomcat), 
  sometimes the login does not work with the same access-deinied page.
 Stranger, if there is code in the SchemeEnforcementFilter for the https, ie 
 always a session it does not happen (as yet!).
 HttpSession session = req.getSession(false);
 if (session == null) {
   session = req.getSession(true);
 }
 Further investigation is needed on this.
 Cheers Greg



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ROL-2056) Wrong pointer (section number) in Install Guide at section 11.2

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2056.
-
   Resolution: Fixed
Fix Version/s: 5.1.2

Fixed -- now using a cross-reference so it should stay up-to-date even as the 
section numbers change.  Thanks for bringing to our attention.

 Wrong pointer (section number) in Install Guide at section 11.2
 ---

 Key: ROL-2056
 URL: https://issues.apache.org/jira/browse/ROL-2056
 Project: Apache Roller
  Issue Type: Documentation
Reporter: Kohei Nozaki
Assignee: Roller Unassigned
Priority: Minor
 Fix For: 5.1.2


 The guide
 (https://github.com/apache/roller/blob/trunk/docs/roller-install-guide.odt)
 said on section 11.2 like that:
 NOTE: You can run the database scripts manually too, see Section 9.4.
 but there's no section 9.4 now,
 I think section 10.2 is correct.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ROL-2057) NPE at PageServlet.doGet() on WildFly

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2057.
-
   Resolution: Fixed
Fix Version/s: 5.1.2

Committed revision 1649453.
Thanks for the patch.  


 NPE at PageServlet.doGet() on WildFly
 -

 Key: ROL-2057
 URL: https://issues.apache.org/jira/browse/ROL-2057
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - General
Affects Versions: 5.1.1
 Environment: WildFly8.2.0.Final
Reporter: Kohei Nozaki
Assignee: Roller Unassigned
 Fix For: 5.1.2

 Attachments: ROL-2057.patch


 After I finish procedures of official installation guide for JBoss,
 and I create a new blog, but the blog can't be visible.
 URLs of the top page or the blog are always returning status 500,
 and many NPEs are dumped on logs. like this:
 snip
 Caused by: java.lang.NullPointerException
at 
 io.undertow.servlet.spec.ServletContextImpl.getMimeType(ServletContextImpl.java:192)
at 
 org.apache.roller.weblogger.ui.rendering.servlets.PageServlet.doGet(PageServlet.java:423)
 snip
 It looks like that the cause is came from WildFly implementation of 
 ServletContext.
 (https://github.com/undertow-io/undertow/blob/master/servlet/src/main/java/io/undertow/servlet/spec/ServletContextImpl.java)
 It has no null-check of the argument.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ROL-2057) Missing NPE check in Roller PageServlet class

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-2057:

Summary: Missing NPE check in Roller PageServlet class  (was: NPE at 
PageServlet.doGet() on WildFly)

 Missing NPE check in Roller PageServlet class
 -

 Key: ROL-2057
 URL: https://issues.apache.org/jira/browse/ROL-2057
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - General
Affects Versions: 5.1.1
 Environment: WildFly8.2.0.Final
Reporter: Kohei Nozaki
Assignee: Roller Unassigned
 Fix For: 5.1.2

 Attachments: ROL-2057.patch


 After I finish procedures of official installation guide for JBoss,
 and I create a new blog, but the blog can't be visible.
 URLs of the top page or the blog are always returning status 500,
 and many NPEs are dumped on logs. like this:
 snip
 Caused by: java.lang.NullPointerException
at 
 io.undertow.servlet.spec.ServletContextImpl.getMimeType(ServletContextImpl.java:192)
at 
 org.apache.roller.weblogger.ui.rendering.servlets.PageServlet.doGet(PageServlet.java:423)
 snip
 It looks like that the cause is came from WildFly implementation of 
 ServletContext.
 (https://github.com/undertow-io/undertow/blob/master/servlet/src/main/java/io/undertow/servlet/spec/ServletContextImpl.java)
 It has no null-check of the argument.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ROL-2052) Custom stylesheets not being updated correctly when user switches between shared and custom themes.

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-2052:

Fix Version/s: 5.1.1

 Custom stylesheets not being updated correctly when user switches between 
 shared and custom themes.
 ---

 Key: ROL-2052
 URL: https://issues.apache.org/jira/browse/ROL-2052
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Roller Unassigned
 Fix For: 5.1.1


 1.) When user goes from a shared theme w/custom stylesheet to custom template 
 importing the same theme, the custom stylesheet gets overwritten.  It should 
 get overwritten only if the imported theme is different than the shared 
 theme, to allow the user to upgrade naturally from sharedcustom stylesheet 
 to custom theme using the shared theme  while not losing the custom 
 stylesheet.
 2.) When user goes from custom to shared theme, the custom stylesheet is not 
 getting obliterated as already happens when the user goes from one shared 
 theme to a different shared theme.  As a result, the custom stylesheet from 
 the custom theme ends up being used with the shared theme, messing up the 
 appearance of the shared theme.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-2052) Custom stylesheets not being updated correctly when user switches between shared and custom themes.

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-2052.
---

 Custom stylesheets not being updated correctly when user switches between 
 shared and custom themes.
 ---

 Key: ROL-2052
 URL: https://issues.apache.org/jira/browse/ROL-2052
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Roller Unassigned
 Fix For: 5.1.1


 1.) When user goes from a shared theme w/custom stylesheet to custom template 
 importing the same theme, the custom stylesheet gets overwritten.  It should 
 get overwritten only if the imported theme is different than the shared 
 theme, to allow the user to upgrade naturally from sharedcustom stylesheet 
 to custom theme using the shared theme  while not losing the custom 
 stylesheet.
 2.) When user goes from custom to shared theme, the custom stylesheet is not 
 getting obliterated as already happens when the user goes from one shared 
 theme to a different shared theme.  As a result, the custom stylesheet from 
 the custom theme ends up being used with the shared theme, messing up the 
 appearance of the shared theme.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-1764) example for plugin model needs to be updated

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1764.
---
Resolution: Cannot Reproduce

Item from 2008.  The class, and the code referenced in the patch, doesn't 
appear to exist today in Roller trunk.

 example for plugin model needs to be updated
 

 Key: ROL-1764
 URL: https://issues.apache.org/jira/browse/ROL-1764
 Project: Apache Roller
  Issue Type: Improvement
  Components: Website and Documentation
Affects Versions: 4.0
Reporter: Ganesh Mathrubootham
Assignee: Roller Unassigned
Priority: Trivial
 Attachments: plugin_model_example_fix.patch


 The sample model to access user object from theme templates doesn't work as 
 is, and needs modification.  This issue was brought up by a user in the 
 mailing list where I had replied with the solution to the poster.  
 http://mail-archives.apache.org/mod_mbox/roller-dev/200812.mbox/%3cdcfa440e0812051409y2c1d3e1by98c298c573144...@mail.gmail.com%3e



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-1167) Authentication failure in Atom API leads to NullPointerException in RollerAtomHandler

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1167.
---
Resolution: Fixed

This item from 2006 against Roller 2.3.  The current Roller trunk already has 
this code in (perhaps from this patch).

 Authentication failure in Atom API leads to NullPointerException in 
 RollerAtomHandler
 -

 Key: ROL-1167
 URL: https://issues.apache.org/jira/browse/ROL-1167
 Project: Apache Roller
  Issue Type: Bug
  Components: Web Services
Affects Versions: 2.3
 Environment: All
Reporter: Padraig O hIceadha
Priority: Minor
 Attachments: ASF.LICENSE.NOT.GRANTED--RollerAtomHandler.java, 
 ASF.LICENSE.NOT.GRANTED--patchfile.txt


 If an incorrect username or password is used ehen e.g. posting a new entry 
 via the Atom API instead of getting a 401 error (Unauthorized) you get a 500 
 server error because of a NullPOinterException in RollerAtomHandler.
 RollerAtomHandler#getAuthenticatedUsername was not checking if this.user was 
 null.
 The patch for my proposed fix is below :
 Index: RollerAtomHandler.java
 ===
 --- RollerAtomHandler.java  (revision 414838)
 +++ RollerAtomHandler.java  (working copy)
 @@ -121,6 +121,9 @@
   * Return weblogHandle of authenticated user or null if there is none.
   */
  public String getAuthenticatedUsername() {
 +if (this.user == null) {
 +return null;
 +}
  return this.user.getUserName();
  }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ROL-2037) Possible breakage in Planet feature

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-2037:

Fix Version/s: (was: 5.1.1)
   5.1.2

 Possible breakage in Planet feature
 ---

 Key: ROL-2037
 URL: https://issues.apache.org/jira/browse/ROL-2037
 Project: Apache Roller
  Issue Type: Bug
  Components: Planet Aggregator
Affects Versions: 5.1
Reporter: David Johnson
Assignee: David Johnson
 Fix For: 5.1.2


 I'm still investigating this and hope to fix for 5.1.
 [EL Warning]: 2014-07-08 17:38:00.199--UnitOfWork(1194666925)--Exception 
 [EclipseLink-4002] (Eclipse Persistence Services - 2.5.1.v20130918-f2b9fc5): 
 org.eclipse.persistence.exceptions.DatabaseException
 Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: 
 Incorrect datetime value: '1969-12-31 19:00:00' for column 'last_updated' at 
 row 1
 Error Code: 1292
 Call: INSERT INTO rag_subscription (id, author, feed_url, inbound_blogs, 
 inbound_links, last_updated, site_url, title) VALUES (?, ?, ?, ?, ?, ?, ?, ?)
 bind = [8 parameters bound]
 Query: InsertObjectQuery({weblogger:project, 
 http://rollerweblogger.org/project/, Roller: free and open source Java blog 
 software, Roller: free and open source Java blog software, Wed Dec 31 
 19:00:00 EST 1969})
 [EL Warning]: 2014-07-08 17:43:00.081--UnitOfWork(1313604468)--Exception 
 [EclipseLink-4002] (Eclipse Persistence Services - 2.5.1.v20130918-f2b9fc5): 
 org.eclipse.persistence.exceptions.DatabaseException
 Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: 
 Incorrect datetime value: '1969-12-31 19:00:00' for column 'last_updated' at 
 row 1
 Error Code: 1292



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-1620) Plus signs in categories lead to a 404 category RSS/Atom feeds

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1620.
---

 Plus signs in categories lead to a 404 category RSS/Atom feeds
 --

 Key: ROL-1620
 URL: https://issues.apache.org/jira/browse/ROL-1620
 Project: Apache Roller
  Issue Type: Bug
  Components: Newsfeeds (RSS  Atom)
Reporter: linda skrocki
Assignee: Glen Mazza
 Fix For: 3.1.1, 5.1.1


 Steps to reproduce:
 1. create a categetory called C++
 2. post an entry to that category
 3. note that the feed for that category results in 404



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-1387) In creating tag aggregate counts, count tags only from published blog entries

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1387.
---

 In creating tag aggregate counts, count tags only from published blog entries
 -

 Key: ROL-1387
 URL: https://issues.apache.org/jira/browse/ROL-1387
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Reporter: linda skrocki
Assignee: Glen Mazza
 Fix For: 5.1.1


 Adjust the functionality so that tags for entries that have a pub date in the 
 future do not show up until the entry is published.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-2055) Comment search should be case insensitive

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-2055.
---

 Comment search should be case insensitive
 -

 Key: ROL-2055
 URL: https://issues.apache.org/jira/browse/ROL-2055
 Project: Apache Roller
  Issue Type: Bug
  Components: Comments
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
Priority: Minor
 Fix For: 5.1.1


 Comment search is presently case sensitive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-2051) Roller not falling back to standard theme renditions when mobile one unavailable.

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-2051.
---

 Roller not falling back to standard theme renditions when mobile one 
 unavailable.
 -

 Key: ROL-2051
 URL: https://issues.apache.org/jira/browse/ROL-2051
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Roller Unassigned
Priority: Critical
 Fix For: 5.1.1


 Roller needs to revert to the standard rendition when the mobile rendition is 
 unavailable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-2054) Newly saved categories not appearing on blog

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-2054.
---

 Newly saved categories not appearing on blog
 

 Key: ROL-2054
 URL: https://issues.apache.org/jira/browse/ROL-2054
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - General
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
 Fix For: 5.1.1


 Weblog object not refreshing its category list after save of a category; 
 necessary to reboot Roller for it to appear.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ROL-2055) Comment search should be case insensitive

[Glen Mazza (JIRA)]

Glen Mazza created ROL-2055:
---

 Summary: Comment search should be case insensitive
 Key: ROL-2055
 URL: https://issues.apache.org/jira/browse/ROL-2055
 Project: Apache Roller
  Issue Type: Bug
  Components: Comments
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
Priority: Minor


Comment search is presently case sensitive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ROL-2055) Comment search should be case insensitive

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2055.
-
   Resolution: Fixed
Fix Version/s: 5.1.1

Fixed - Revision 1627429

 Comment search should be case insensitive
 -

 Key: ROL-2055
 URL: https://issues.apache.org/jira/browse/ROL-2055
 Project: Apache Roller
  Issue Type: Bug
  Components: Comments
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
Priority: Minor
 Fix For: 5.1.1


 Comment search is presently case sensitive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ROL-1387) Tags of unpublished entries show in tag cloud

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza reassigned ROL-1387:
---

Assignee: Glen Mazza  (was: Roller Unassigned)

 Tags of unpublished entries show in tag cloud
 -

 Key: ROL-1387
 URL: https://issues.apache.org/jira/browse/ROL-1387
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Reporter: linda skrocki
Assignee: Glen Mazza

 Adjust the functionality so that tags for entries that have a pub date in the 
 future do not show up until the entry is published.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ROL-1387) In creating tag aggregate counts, count tags only from published blog entries

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-1387:

Summary: In creating tag aggregate counts, count tags only from published 
blog entries  (was: Tags of unpublished entries show in tag cloud)

 In creating tag aggregate counts, count tags only from published blog entries
 -

 Key: ROL-1387
 URL: https://issues.apache.org/jira/browse/ROL-1387
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Reporter: linda skrocki
Assignee: Glen Mazza

 Adjust the functionality so that tags for entries that have a pub date in the 
 future do not show up until the entry is published.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-1719) Field locale not filled when creating weblog entry via APP

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1719.
---
Resolution: Unresolved

Item is from 2008 against old versions of both Roller and Abdera.  Recent 
testing of Roller 5.1 with blog client software revealed no problems.  We can 
take another JIRA report on this issue if it occurs with the latest versions of 
Abdera and Roller.

 Field locale not filled when creating weblog entry via APP
 --

 Key: ROL-1719
 URL: https://issues.apache.org/jira/browse/ROL-1719
 Project: Apache Roller
  Issue Type: Bug
  Components: Newsfeeds (RSS  Atom)
Affects Versions: 4.0
 Environment: Roller 4.0 running on Windows and accessed through 
 Abdera 0.4
Reporter: Hubert Vogten
Assignee: Roller Unassigned

 When creating a new weblog entry via APP using the 0.4 version of abdera the 
 locale field is not set. Although modifying this entry through APP afterwards 
 is no problem, it is impossible to edit this entry via the normal UI of 
 Roller. An error Locale is a required field is reported.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-1594) SearchServlet initialize pageRequest without authenticatedUser info, cause $url.isAuthenticatedAsAdmin function

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1594.
---
Resolution: Incomplete

I'm not sure why that authenticated user is necessary when making a blog entry 
search request, and the author isn't giving any reason for it.

 SearchServlet initialize pageRequest without authenticatedUser info, cause 
 $url.isAuthenticatedAsAdmin function 
 

 Key: ROL-1594
 URL: https://issues.apache.org/jira/browse/ROL-1594
 Project: Apache Roller
  Issue Type: Bug
  Components: Authentication, Roles and Access Controls
Affects Versions: 4.0
Reporter: Miles Huang
Assignee: Roller Unassigned
 Attachments: ASF.LICENSE.NOT.GRANTED--SearchServlet.patch


 SearchServlet initialize a mock pageRequest based on parsed searchRequest, 
 but without authenticUser info. Some model methods rely on it, such as 
 $url.isUserAuthorizedToAuthor().



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ROL-2054) Newly saved categories not appearing on blog

[Glen Mazza (JIRA)]

Glen Mazza created ROL-2054:
---

 Summary: Newly saved categories not appearing on blog
 Key: ROL-2054
 URL: https://issues.apache.org/jira/browse/ROL-2054
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - General
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza


Weblog object not refreshing its category list after save of a category; 
necessary to reboot Roller for it to appear.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ROL-2054) Newly saved categories not appearing on blog

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2054.
-
   Resolution: Fixed
Fix Version/s: 5.1.1

Fixed - r1623597

 Newly saved categories not appearing on blog
 

 Key: ROL-2054
 URL: https://issues.apache.org/jira/browse/ROL-2054
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - General
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
 Fix For: 5.1.1


 Weblog object not refreshing its category list after save of a category; 
 necessary to reboot Roller for it to appear.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (ROL-1708) AtomPub problems with Windows Live Writer

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1708.
---
Resolution: Unresolved

Item is from 2008.  Closing as unresolved, if a current user is having a 
problem with a recent version of WLW and Roller a new JIRA can be entered.

 AtomPub problems with Windows Live Writer
 -

 Key: ROL-1708
 URL: https://issues.apache.org/jira/browse/ROL-1708
 Project: Apache Roller
  Issue Type: Bug
  Components: Web Services
Affects Versions: 4.0
Reporter: David Johnson
Priority: Minor

Windows Live Writer + Atom (as discussed before)
What it calls Categories are posted as Tags
Going to look at an entry created by the post brings up a few weird 
 issues.
1 - the default language is whatever is first in the list Albanian
2 - Category  is the defined default for the system.
Changing this category then attempting a republish causes it to create 
 a new
article.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ROL-2052) Custom stylesheets not being updated correctly when user switches between shared and custom themes.

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2052.
-
Resolution: Fixed

Fixed -  revision 1622537

 Custom stylesheets not being updated correctly when user switches between 
 shared and custom themes.
 ---

 Key: ROL-2052
 URL: https://issues.apache.org/jira/browse/ROL-2052
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Roller Unassigned

 1.) When user goes from a shared theme w/custom stylesheet to custom template 
 importing the same theme, the custom stylesheet gets overwritten.  It should 
 get overwritten only if the imported theme is different than the shared 
 theme, to allow the user to upgrade naturally from sharedcustom stylesheet 
 to custom theme using the shared theme  while not losing the custom 
 stylesheet.
 2.) When user goes from custom to shared theme, the custom stylesheet is not 
 getting obliterated as already happens when the user goes from one shared 
 theme to a different shared theme.  As a result, the custom stylesheet from 
 the custom theme ends up being used with the shared theme, messing up the 
 appearance of the shared theme.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ROL-2051) Roller not falling back to standard theme renditions when mobile one unavailable.

[Glen Mazza (JIRA)]

Glen Mazza created ROL-2051:
---

 Summary: Roller not falling back to standard theme renditions when 
mobile one unavailable.
 Key: ROL-2051
 URL: https://issues.apache.org/jira/browse/ROL-2051
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Roller Unassigned
Priority: Critical


Roller needs to revert to the standard rendition when the mobile device type is 
unavailable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ROL-2051) Roller not falling back to standard theme renditions when mobile one unavailable.

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-2051:

  Description: Roller needs to revert to the standard rendition when the 
mobile rendition is unavailable.  (was: Roller needs to revert to the standard 
rendition when the mobile device type is unavailable.)
Fix Version/s: 5.1.1

 Roller not falling back to standard theme renditions when mobile one 
 unavailable.
 -

 Key: ROL-2051
 URL: https://issues.apache.org/jira/browse/ROL-2051
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Roller Unassigned
Priority: Critical
 Fix For: 5.1.1


 Roller needs to revert to the standard rendition when the mobile rendition is 
 unavailable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (ROL-2051) Roller not falling back to standard theme renditions when mobile one unavailable.

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2051.
-
Resolution: Fixed

Fixed - revision 1622082

 Roller not falling back to standard theme renditions when mobile one 
 unavailable.
 -

 Key: ROL-2051
 URL: https://issues.apache.org/jira/browse/ROL-2051
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Roller Unassigned
Priority: Critical
 Fix For: 5.1.1


 Roller needs to revert to the standard rendition when the mobile rendition is 
 unavailable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ROL-2050) Page action with Admin management panel

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14116588#comment-14116588
 ] 

Glen Mazza commented on ROL-2050:
-

Hi Tamas, I made a small change in Roller trunk (future 5.1.1) that might help 
you a bit.  Now, if the weblog is using a custom theme, the Design tab and 
Theme link on the Main Menu will link directly to the Templates page instead 
of the ThemeEdit page (where you pick shared or custom).  So at least you no 
longer need to click from ThemeEdit to Templates to get to your pages.

 Page action with Admin management panel
 ---

 Key: ROL-2050
 URL: https://issues.apache.org/jira/browse/ROL-2050
 Project: Apache Roller
  Issue Type: New Feature
  Components: User Interface - Weblog Editor
Affects Versions: 5.0.4
 Environment: Tomcat 7.055 - Ubuntu
Reporter: Tamas Balazs
Assignee: Roller Unassigned
Priority: Minor
 Fix For: 5.1.1


 Hi,
 I am trying to add multiple pages to a weblog. the reason of adding pages 
 instead of entries is simple - the content of these are not articles but 
 dynamically loading JS-like frontend applications. The reasons I cannot add 
 them into entries are simple - if these pages show up the applications 
 start loading in immediately, which would cause a bit of a mayhem with all of 
 their music, movies, maps etc. Also I don't want to limit the number of 
 entries to be shown just for the sake of these. Unfortunately I cannot make 
 these applications to run after user initiated JS input (ie. I cannot create 
 Click here to start button as the third party app will just not work with 
 them).
 Cut the long story short, I would like to add Pages to the blog. Currently 
 the only way I can do is (as far as I know) is that I add custom templates 
 for each individual pages. This is fine(ish) for now as I have only 10-12 
 pages, but this number is likely to go up in the future.
 Obviously there is always a workaround to my issue (setting up another blog, 
 tailor its presentation layer that meets the third party apps requirements 
 and then link the these elements as entries, etc.) but to be honest every 
 major blog-management system has this page feature and I would be grateful 
 to see this coming in the forthcoming release. I guess in layman's terms what 
 I would be happy to see is an option under the CreateEdit section for 
 Page, which then can create the feature in accordance with its template 
 action. Regarding creating their index I don't think the first release of 
 this improvement need to go too far on that - if there is a Velocity 
 macro/script doing some basic page url/name listings that will be sufficient.
 On the other hand there might be a similar solution somewhere in the Roller 
 docs and I have just couldn't find it so far - in this case please let me 
 know what I am doing wrong.
 Thanks



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-2049) Cannot log-in to control panel via Tomcat virtual host TLD - have to use IP-location

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-2049.
---

Resolution: Not a Problem

The Roller JIRA is not a place for questions -- first ask on the Roller User's 
Mailing List.  Also, you need to look into upgrading to Roller 5.1, there won't 
be a Roller 5.0.5 (its libraries are too old and it's too messy to work with) 
so we wouldn't fix anything even if there was indeed a problem with it.  
Problems with 5.1, however, we're interested in hearing.

One potential thing to look at is that the blog server admin page does have an 
absolute url to site field, which for my blog at 
https://web-gmazza.rhcloud.com/blog/ is https://web-gmazza.rhcloud.com -- have 
you filled in that field (it's normally needed if you're using https:// for 
example.)  That might be a solution for you.

 Cannot log-in to control panel via Tomcat virtual host TLD - have to use 
 IP-location 
 -

 Key: ROL-2049
 URL: https://issues.apache.org/jira/browse/ROL-2049
 Project: Apache Roller
  Issue Type: Question
  Components: User Interface - Weblog Editor
Affects Versions: 5.0.4
 Environment: Ubuntu - Tomcat 7.055 - MySQL
Reporter: Tamas Balazs
Assignee: Roller Unassigned
Priority: Minor

 I cannot bring the login or the management panel in via the TLD of my site 
 (regardless I use http or https). I can login by using the IP address but 
 that makes everything slightly difficult - ie when pings are sent with my IP 
 as referer instead od TLD, when I try to add image to an article it links in 
 with the IP, etc, etc.
 When I try to login by using my TLD I got nothing - blank white screen. 
 Obviously it makes no difference what sort of browser I use to login...
 Has any of you guys got any ideas how to solve this issue?
 Thanks...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-2050) Page action with Admin management panel

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-2050.
---

Resolution: Won't Fix

Have you considered entering in text in the summary field for each blog entry 
where you want to suppress the multimedia explosion you describe?  For the main 
weblog page containing maybe 15 blog articles, that triggers a read more 
button for each blog article, requiring the user to click on it to see the 
single blog article with all the activating graphics.  That you have not 
mentioned using the summary field--the most obvious solution--indicates you may 
not have been aware of it.

We do provide a page system as you know which takes care of most user needs 
when they need to deviate a bit beyond blog entries.  To go beyond that would 
be to turn Roller into a web application framework, outside our mission.  At 
that stage you don't need a blog server but a more generalized CMS framework.

 Page action with Admin management panel
 ---

 Key: ROL-2050
 URL: https://issues.apache.org/jira/browse/ROL-2050
 Project: Apache Roller
  Issue Type: New Feature
  Components: User Interface - Weblog Editor
Affects Versions: 5.0.4
 Environment: Tomcat 7.055 - Ubuntu
Reporter: Tamas Balazs
Assignee: Roller Unassigned
Priority: Minor
 Fix For: 5.1.1


 Hi,
 I am trying to add multiple pages to a weblog. the reason of adding pages 
 instead of entries is simple - the content of these are not articles but 
 dynamically loading JS-like frontend applications. The reasons I cannot add 
 them into entries are simple - if these pages show up the applications 
 start loading in immediately, which would cause a bit of a mayhem with all of 
 their music, movies, maps etc. Also I don't want to limit the number of 
 entries to be shown just for the sake of these. Unfortunately I cannot make 
 these applications to run after user initiated JS input (ie. I cannot create 
 Click here to start button as the third party app will just not work with 
 them).
 Cut the long story short, I would like to add Pages to the blog. Currently 
 the only way I can do is (as far as I know) is that I add custom templates 
 for each individual pages. This is fine(ish) for now as I have only 10-12 
 pages, but this number is likely to go up in the future.
 Obviously there is always a workaround to my issue (setting up another blog, 
 tailor its presentation layer that meets the third party apps requirements 
 and then link the these elements as entries, etc.) but to be honest every 
 major blog-management system has this page feature and I would be grateful 
 to see this coming in the forthcoming release. I guess in layman's terms what 
 I would be happy to see is an option under the CreateEdit section for 
 Page, which then can create the feature in accordance with its template 
 action. Regarding creating their index I don't think the first release of 
 this improvement need to go too far on that - if there is a Velocity 
 macro/script doing some basic page url/name listings that will be sufficient.
 On the other hand there might be a similar solution somewhere in the Roller 
 docs and I have just couldn't find it so far - in this case please let me 
 know what I am doing wrong.
 Thanks



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (ROL-2050) Page action with Admin management panel

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14113275#comment-14113275
 ] 

Glen Mazza commented on ROL-2050:
-

Another question, are you sure what you're doing wouldn't be better suited for 
a Wiki like JSPWiki?  Blogs consist of entries, but Wikis consist of pages.

 Page action with Admin management panel
 ---

 Key: ROL-2050
 URL: https://issues.apache.org/jira/browse/ROL-2050
 Project: Apache Roller
  Issue Type: New Feature
  Components: User Interface - Weblog Editor
Affects Versions: 5.0.4
 Environment: Tomcat 7.055 - Ubuntu
Reporter: Tamas Balazs
Assignee: Roller Unassigned
Priority: Minor
 Fix For: 5.1.1


 Hi,
 I am trying to add multiple pages to a weblog. the reason of adding pages 
 instead of entries is simple - the content of these are not articles but 
 dynamically loading JS-like frontend applications. The reasons I cannot add 
 them into entries are simple - if these pages show up the applications 
 start loading in immediately, which would cause a bit of a mayhem with all of 
 their music, movies, maps etc. Also I don't want to limit the number of 
 entries to be shown just for the sake of these. Unfortunately I cannot make 
 these applications to run after user initiated JS input (ie. I cannot create 
 Click here to start button as the third party app will just not work with 
 them).
 Cut the long story short, I would like to add Pages to the blog. Currently 
 the only way I can do is (as far as I know) is that I add custom templates 
 for each individual pages. This is fine(ish) for now as I have only 10-12 
 pages, but this number is likely to go up in the future.
 Obviously there is always a workaround to my issue (setting up another blog, 
 tailor its presentation layer that meets the third party apps requirements 
 and then link the these elements as entries, etc.) but to be honest every 
 major blog-management system has this page feature and I would be grateful 
 to see this coming in the forthcoming release. I guess in layman's terms what 
 I would be happy to see is an option under the CreateEdit section for 
 Page, which then can create the feature in accordance with its template 
 action. Regarding creating their index I don't think the first release of 
 this improvement need to go too far on that - if there is a Velocity 
 macro/script doing some basic page url/name listings that will be sufficient.
 On the other hand there might be a similar solution somewhere in the Roller 
 docs and I have just couldn't find it so far - in this case please let me 
 know what I am doing wrong.
 Thanks



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (ROL-2037) Possible breakage in Planet feature

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-2037:


Fix Version/s: (was: 5.1)
   5.1.1

 Possible breakage in Planet feature
 ---

 Key: ROL-2037
 URL: https://issues.apache.org/jira/browse/ROL-2037
 Project: Apache Roller
  Issue Type: Bug
  Components: Planet Aggregator
Affects Versions: 5.1
Reporter: David Johnson
Assignee: David Johnson
 Fix For: 5.1.1


 I'm still investigating this and hope to fix for 5.1.
 [EL Warning]: 2014-07-08 17:38:00.199--UnitOfWork(1194666925)--Exception 
 [EclipseLink-4002] (Eclipse Persistence Services - 2.5.1.v20130918-f2b9fc5): 
 org.eclipse.persistence.exceptions.DatabaseException
 Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: 
 Incorrect datetime value: '1969-12-31 19:00:00' for column 'last_updated' at 
 row 1
 Error Code: 1292
 Call: INSERT INTO rag_subscription (id, author, feed_url, inbound_blogs, 
 inbound_links, last_updated, site_url, title) VALUES (?, ?, ?, ?, ?, ?, ?, ?)
 bind = [8 parameters bound]
 Query: InsertObjectQuery({weblogger:project, 
 http://rollerweblogger.org/project/, Roller: free and open source Java blog 
 software, Roller: free and open source Java blog software, Wed Dec 31 
 19:00:00 EST 1969})
 [EL Warning]: 2014-07-08 17:43:00.081--UnitOfWork(1313604468)--Exception 
 [EclipseLink-4002] (Eclipse Persistence Services - 2.5.1.v20130918-f2b9fc5): 
 org.eclipse.persistence.exceptions.DatabaseException
 Internal Exception: com.mysql.jdbc.MysqlDataTruncation: Data truncation: 
 Incorrect datetime value: '1969-12-31 19:00:00' for column 'last_updated' at 
 row 1
 Error Code: 1292



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1844) MediaFileAddSuccess Form

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1844.
---


 MediaFileAddSuccess Form 
 -

 Key: ROL-1844
 URL: https://issues.apache.org/jira/browse/ROL-1844
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - General
Affects Versions: 5.0
Reporter: David Driscoll
Assignee: Greg Huber
 Attachments: applicationResources_patch20091030.patch, 
 mediaFileAddSuccess_patch20091030.patch, screenshot_drpdown.jpg


 After I  pulling the latest trunk code, and building , I tried out the new 
 media file stuff.
 I ran into a small UI bug.
 When I click on Media Files, I successfully uploaded a image file, and ended 
 up on the MediaFileAddSuccess.jsp page.
 On this page there is a button Create Post with Image, I click this and it 
 redirects to the blog entry page, but it does not
 include the image file.
 Since I was in debug mode, I noticed that java class: EntryAddWithMediaFile, 
 method: Execute expects a value for type, but
 the page MediaFileAddSuccess.jsp does not have a type checkbox or dropdown 
 that sets the type.
 I have included a patch for MediaFileAddSuccess.jsp that adds a dropdown for 
 users to select either a type of weblog or podcast and additional text 
 for the dropdown's title in ApplicationResources patch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (ROL-1926) Comment notifcation emails being sent before comment approval

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-1926:


Fix Version/s: 5.0.4

 Comment notifcation emails being sent before comment approval
 -

 Key: ROL-1926
 URL: https://issues.apache.org/jira/browse/ROL-1926
 Project: Apache Roller
  Issue Type: Bug
  Components: Comments
Affects Versions: 4.0, 5.0
 Environment: Any 4.0 or 5.0 instance
Reporter: David Johnson
Assignee: David Johnson
 Fix For: 5.0.4


 I'm noticing that if I subscribe to be notified of new comments for an
 entry, I am getting emails even before they are approved.
 I'm running Roller 4.0.1 on Oracle DB and WLS11g.
 Comment authentication is required globally. Require comment moderation for
 all weblogs is checked in server admin area
 Steps taken:
 1. Create a comment on entry page and provide email and check Notify me by
 email of new comments.
 2. As an admin, go into the blog comment area. Ensure that it is Pending.
 See also email message: http://markmail.org/message/wvkzsd2lej33aw7d



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (ROL-1979) Remove subcategory functionality from Roller 5.1

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-1979:


Fix Version/s: 5.1

 Remove subcategory functionality from Roller 5.1
 

 Key: ROL-1979
 URL: https://issues.apache.org/jira/browse/ROL-1979
 Project: Apache Roller
  Issue Type: Task
  Components: User Interface - General
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
 Fix For: 5.1


 Keep categories top-level as befits the vast majority of blogs.  As part of 
 switch to allow for sorting/ordering categories instead of present random 
 order.
 See: http://markmail.org/message/phicusgyz2nazaab



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1151) Remove getConfigManager from Roller interface

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1151.
---


 Remove getConfigManager from Roller interface
 -

 Key: ROL-1151
 URL: https://issues.apache.org/jira/browse/ROL-1151
 Project: Apache Roller
  Issue Type: Improvement
Affects Versions: 2.0.1
Reporter: Craig L Russell
Assignee: Glen Mazza

 The ConfigManager interface itself is deprecated, yet it is still referenced 
 by the Roller interface. So every implementation of Roller must implement a 
 deprecated method.
 The only usage in the current trunk is in HibernatePropertiesManagerImpl 
 where it is used in case of migration of old properties. This usage can be 
 changed to use a method defined in HibernateRollerImpl instead of the public 
 Roller method.
 If this is the right fix, I'll be happy to provide a patch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1926) Comment notifcation emails being sent before comment approval

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1926.
---


 Comment notifcation emails being sent before comment approval
 -

 Key: ROL-1926
 URL: https://issues.apache.org/jira/browse/ROL-1926
 Project: Apache Roller
  Issue Type: Bug
  Components: Comments
Affects Versions: 4.0, 5.0
 Environment: Any 4.0 or 5.0 instance
Reporter: David Johnson
Assignee: David Johnson
 Fix For: 5.0.4


 I'm noticing that if I subscribe to be notified of new comments for an
 entry, I am getting emails even before they are approved.
 I'm running Roller 4.0.1 on Oracle DB and WLS11g.
 Comment authentication is required globally. Require comment moderation for
 all weblogs is checked in server admin area
 Steps taken:
 1. Create a comment on entry page and provide email and check Notify me by
 email of new comments.
 2. As an admin, go into the blog comment area. Ensure that it is Pending.
 See also email message: http://markmail.org/message/wvkzsd2lej33aw7d



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1979) Remove subcategory functionality from Roller 5.1

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1979.
---


 Remove subcategory functionality from Roller 5.1
 

 Key: ROL-1979
 URL: https://issues.apache.org/jira/browse/ROL-1979
 Project: Apache Roller
  Issue Type: Task
  Components: User Interface - General
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
 Fix For: 5.1


 Keep categories top-level as befits the vast majority of blogs.  As part of 
 switch to allow for sorting/ordering categories instead of present random 
 order.
 See: http://markmail.org/message/phicusgyz2nazaab



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (ROL-1554) Listing Box Invite a new user to join... does not have a horizontal scrolling bar

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-1554:


Fix Version/s: 5.1

 Listing Box Invite a new user to join... does not have a horizontal 
 scrolling bar
 ---

 Key: ROL-1554
 URL: https://issues.apache.org/jira/browse/ROL-1554
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - Weblog Editor
Affects Versions: 4.0
 Environment: glassfish - winXP
Reporter: Davis Nguyen
Assignee: Glen Mazza
 Fix For: 5.1


 The Listing Box Invite a new user to join this weblog does not have a 
 horizontal scrolling bar
 STEPS TO REPRODUCE:
 1. Install Glassfish V2 server build 58c
 2. Install Roller M1 b04 build
 3. Start Roller  Register an admin user  create a Weblog and a web log entry
 4. Register another user as listed below:
  Username:  ThisIsATestForGroupBlog
  Password: test
  Password (confirm) test
 Screen name: grouptest
 Full Name: Group Test
 Email: glassfish.apache.roller.java@sun.com
 5. Go to Preferences tab  Members  Invite New Member 
 BUG:
  Can not view the user ThisIsATestForGroupBlog email alias
 




--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1554) Listing Box Invite a new user to join... does not have a horizontal scrolling bar

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1554.
---


 Listing Box Invite a new user to join... does not have a horizontal 
 scrolling bar
 ---

 Key: ROL-1554
 URL: https://issues.apache.org/jira/browse/ROL-1554
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - Weblog Editor
Affects Versions: 4.0
 Environment: glassfish - winXP
Reporter: Davis Nguyen
Assignee: Glen Mazza
 Fix For: 5.1


 The Listing Box Invite a new user to join this weblog does not have a 
 horizontal scrolling bar
 STEPS TO REPRODUCE:
 1. Install Glassfish V2 server build 58c
 2. Install Roller M1 b04 build
 3. Start Roller  Register an admin user  create a Weblog and a web log entry
 4. Register another user as listed below:
  Username:  ThisIsATestForGroupBlog
  Password: test
  Password (confirm) test
 Screen name: grouptest
 Full Name: Group Test
 Email: glassfish.apache.roller.java@sun.com
 5. Go to Preferences tab  Members  Invite New Member 
 BUG:
  Can not view the user ThisIsATestForGroupBlog email alias
 




--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1640) Support of add'l web2.0 macros

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1640.
---


 Support of add'l web2.0 macros
 --

 Key: ROL-1640
 URL: https://issues.apache.org/jira/browse/ROL-1640
 Project: Apache Roller
  Issue Type: Improvement
Reporter: linda skrocki
Assignee: Glen Mazza

 The following macros are supported on Roller:
  #showDeliciousPostIcon($entry) - Bookmark the the entry on del.icio.us
  #showFurlPostIcon($entry) - Bookmark the entry on Furl
  #showSimpyPostIcon($entry) - Bookmark the entry on Simpy
  #showSlashdotPostIcon($entry) - Submit the entry to the editors at Slashdot
  #showTechnoratiSearchIcon($entry) - Show all blog posts that link to your 
 entry
  #showDiggPostIcon($entry) - Digg your entry on Digg.com
 This CR is to also support the following:
 #showRedditPostIcon($entry) 
 #showStumbleUponPostIcon($entry)
 #showFacebookPostIcon($entry)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (ROL-1981) Allow user to specify order of blog categories

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-1981:


Fix Version/s: 5.1

 Allow user to specify order of blog categories
 --

 Key: ROL-1981
 URL: https://issues.apache.org/jira/browse/ROL-1981
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - General
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
 Fix For: 5.1


 Roller presently does not allow user to specify left to right display order 
 of blog categories -- when they are added, they are reinserted in arbitrary 
 locations in the category table.  Provide at least a minimal ability to 
 control ordering by having all new categories be placed at the end.  Will 
 probably need to create a new position (integer) column in the weblog 
 category table to store the desired display order.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-2017) Unable to use connection pool

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-2017.
---


 Unable to use connection pool
 -

 Key: ROL-2017
 URL: https://issues.apache.org/jira/browse/ROL-2017
 Project: Apache Roller
  Issue Type: Bug
  Components: Data Model  JPA Backend
Affects Versions: 5.0.3
Reporter: David Johnson
Assignee: David Johnson

 Something has changed in Roller 5 that is now preventing the use of a JNDI 
 based database, and this (apparently) prevents the use of a connection pool 
 with Roller -- and is impacting blogs.apache.org stability.
 There is some additional discussion here:
 http://roller.markmail.org/thread/qe6hr3wx6qzokhxk



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (ROL-1999) Switch from Referrers to storing tracking codes (e.g., Google Analytics)

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-1999:


Fix Version/s: 5.1

 Switch from Referrers to storing tracking codes (e.g., Google Analytics)
 

 Key: ROL-1999
 URL: https://issues.apache.org/jira/browse/ROL-1999
 Project: Apache Roller
  Issue Type: Improvement
  Components: Pings and Trackbacks
Reporter: Glen Mazza
Assignee: Roller Unassigned
 Fix For: 5.1


 Allow for storage of a tracking code (either Google Analytics or its 
 competitors) at both the server admin (a default tracking code) and 
 individual blog level (to serve as an override) on their respective Settings 
 pages.  At the server admin level, provide a checkbox allowing/disallowing 
 individual blog overrides; if disallowed, have the blog-level override field 
 disappear from the Settings view.  Update the default themes that Roller 
 ships with to output the appropriate tracking key if provided.  Then, remove 
 the Referrers functionality from Roller (database table, GUI screen, JPA 
 class, etc.)
 See:  http://markmail.org/message/vgtdjmacceurmbpm



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1999) Switch from Referrers to storing tracking codes (e.g., Google Analytics)

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1999.
---


 Switch from Referrers to storing tracking codes (e.g., Google Analytics)
 

 Key: ROL-1999
 URL: https://issues.apache.org/jira/browse/ROL-1999
 Project: Apache Roller
  Issue Type: Improvement
  Components: Pings and Trackbacks
Reporter: Glen Mazza
Assignee: Roller Unassigned
 Fix For: 5.1


 Allow for storage of a tracking code (either Google Analytics or its 
 competitors) at both the server admin (a default tracking code) and 
 individual blog level (to serve as an override) on their respective Settings 
 pages.  At the server admin level, provide a checkbox allowing/disallowing 
 individual blog overrides; if disallowed, have the blog-level override field 
 disappear from the Settings view.  Update the default themes that Roller 
 ships with to output the appropriate tracking key if provided.  Then, remove 
 the Referrers functionality from Roller (database table, GUI screen, JPA 
 class, etc.)
 See:  http://markmail.org/message/vgtdjmacceurmbpm



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-2039) Rename webpage and roller_templatecode tables

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-2039.
---


 Rename webpage and roller_templatecode tables
 -

 Key: ROL-2039
 URL: https://issues.apache.org/jira/browse/ROL-2039
 Project: Apache Roller
  Issue Type: Task
  Components: Data Model  JPA Backend
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
 Fix For: 5.1


 Rename weblog table to custom_template and roller_templatecode to 
 custom_template_rendition  corresponding POJO change in code to better 
 clarify their purpose.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1980) When deleting categories, Roller allows you to move its entries to invisible root category.

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1980.
---


 When deleting categories, Roller allows you to move its entries to invisible 
 root category.
 -

 Key: ROL-1980
 URL: https://issues.apache.org/jira/browse/ROL-1980
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - General
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
 Fix For: 5.1


 The category options available when one creates a new blog entry (not 
 including root) should be the same when moving blog entries to a different 
 category as a result of deleting that category.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1973) ROME dependency used by Roller needs updating

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1973.
---


 ROME dependency used by Roller needs updating
 -

 Key: ROL-1973
 URL: https://issues.apache.org/jira/browse/ROL-1973
 Project: Apache Roller
  Issue Type: Bug
Reporter: Glen Mazza
Assignee: David Johnson
Priority: Minor
 Fix For: 5.1


 An mvn clean install of Roller Trunk reports this error:
 [INFO] 
 
 [INFO] Building Roller app 5.1.0-SNAPSHOT
 [INFO] 
 
 Downloading: 
 http://repo.maven.apache.org/maven2/net/java/dev/rome/rome/1.0/rome-1.0.pom
 [WARNING] The POM for net.java.dev.rome:rome:jar:1.0 is missing, no 
 dependency information available
 One of the ROME jars is including a nonexistent dependency (IIRC it should be 
 version 1.0.0 or something like that), a patch needs to be sent to the ROME 
 team and a new version made.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1963) JPA errors while installing Roller trunk on JBoss 6.1 EAP

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1963.
---


 JPA errors while installing Roller trunk on JBoss 6.1 EAP 
 --

 Key: ROL-1963
 URL: https://issues.apache.org/jira/browse/ROL-1963
 Project: Apache Roller
  Issue Type: Bug
  Components: Installation  Configuration
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza

 Using MySQL 5.5, JDK 7, Ubuntu 12.04, JBoss Enterprise Application Platform 
 6.1.0.Final (http://www.jboss.org/jbossas/downloads/) and Roller trunk.   
 I've installed Roller trunk following the updated instructions in the trunk 
 install guide: 
 http://svn.apache.org/viewvc/roller/trunk/weblogger-docs/installguide/
 As far as I can tell, datasource and JavaMail configured correctly.  Problem 
 is that the JBoss' JPA implementation seems pickier than the OpenJPA used by 
 Tomcat.  Deploying the JBoss Roller WAR gives this error:
 Internal Server Error
 {
 outcome = failed,
 failure-description = {JBAS014671: Failed services = 
 {jboss.persistenceunit.\roller.war#RollerPU\ = 
 org.jboss.msc.service.StartException in service 
 jboss.persistenceunit.\roller.war#RollerPU\: 
 javax.persistence.PersistenceException: [PersistenceUnit: RollerPU] Unable to 
 build EntityManagerFactory
 Caused by: javax.persistence.PersistenceException: [PersistenceUnit: 
 RollerPU] Unable to build EntityManagerFactory
 Caused by: org.hibernate.AnnotationException: @OneToOne or @ManyToOne on 
 org.apache.roller.weblogger.pojos.AutoPing.pingTarget references an unknown 
 entity: org.apache.roller.weblogger.pojos.PingTarget}},
 rolled-back = true
 }
 To fix this, I need to:
 1.) Add PingTarget as a class to persistence.xml 
 (http://svn.apache.org/viewvc/roller/trunk/weblogger-business/src/main/resources/META-INF/persistence.xml?view=markup)
   
 classorg.apache.roller.weblogger.pojos.PingTarget/class
 2.) In PingTarget 
 (http://svn.apache.org/viewvc/roller/trunk/weblogger-business/src/main/java/org/apache/roller/weblogger/pojos/PingTarget.java?view=markup),
  addannotation @javax.persistence.Entity to class and annotation 
 @javax.persistence.Id to PingTarget.getId().
 That seems to fix it, because when I run it again JBoss complains about the 
 next class lacking a class definition:
 Internal Server Error
 {
 outcome = failed,
 failure-description = {JBAS014671: Failed services = 
 {jboss.persistenceunit.\roller-5.1.0-SNAPSHOT-jboss.war#RollerPU\ = 
 org.jboss.msc.service.StartException in service 
 jboss.persistenceunit.\roller-5.1.0-SNAPSHOT-jboss.war#RollerPU\: 
 javax.persistence.PersistenceException: [PersistenceUnit: RollerPU] Unable to 
 build EntityManagerFactory
 Caused by: javax.persistence.PersistenceException: [PersistenceUnit: 
 RollerPU] Unable to build EntityManagerFactory
 Caused by: org.hibernate.AnnotationException: @OneToOne or @ManyToOne on 
 org.apache.roller.weblogger.pojos.AutoPing.website references an unknown 
 entity: org.apache.roller.weblogger.pojos.Weblog}},
 rolled-back = true
 }
 Problem is there's about 20 other classes lacking a class definition in 
 persistence.xml -- unsure if I really should be adding them all in, and if I 
 did so, if I'd end up breaking the JPA as running on Tomcat and GlassFish as 
 a result.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (ROL-1973) ROME dependency used by Roller needs updating

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-1973:


Fix Version/s: 5.1

 ROME dependency used by Roller needs updating
 -

 Key: ROL-1973
 URL: https://issues.apache.org/jira/browse/ROL-1973
 Project: Apache Roller
  Issue Type: Bug
Reporter: Glen Mazza
Assignee: David Johnson
Priority: Minor
 Fix For: 5.1


 An mvn clean install of Roller Trunk reports this error:
 [INFO] 
 
 [INFO] Building Roller app 5.1.0-SNAPSHOT
 [INFO] 
 
 Downloading: 
 http://repo.maven.apache.org/maven2/net/java/dev/rome/rome/1.0/rome-1.0.pom
 [WARNING] The POM for net.java.dev.rome:rome:jar:1.0 is missing, no 
 dependency information available
 One of the ROME jars is including a nonexistent dependency (IIRC it should be 
 version 1.0.0 or something like that), a patch needs to be sent to the ROME 
 team and a new version made.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1942) Uploaded media file not selectable in media file view

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1942.
---


 Uploaded media file not selectable in media file view
 -

 Key: ROL-1942
 URL: https://issues.apache.org/jira/browse/ROL-1942
 Project: Apache Roller
  Issue Type: Bug
  Components: Media files / uploads
Affects Versions: 5.0
 Environment: Linux, Glassfish 3.1.2
Reporter: Budi Ariyanto
Assignee: Greg Huber
  Labels: upload
 Fix For: 5.1

 Attachments: back_to_mediafile_view.png, filedeleted.png, 
 uploadsuccess.png


 I use apache roller 5.0 for javaee.
 Step to reproduce:
 1. Login as a user or admin
 2. Go to Create  Edit -- Media Files
 3. Create a folder and open it
 4. Click Add media file and upload images you want to
 5. After upload success message shown, go back to media file view
 The file that just uploaded not appear and not selectable in the media file 
 view, but if I search it using search tool it can be found.
 If I restart glassfish, the file correctly appear in the media file view.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (ROL-1974) Roller's ROME Propono dependency needs updating to use newer JARs

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-1974:


Fix Version/s: 5.1

 Roller's ROME Propono dependency needs updating to use newer JARs
 -

 Key: ROL-1974
 URL: https://issues.apache.org/jira/browse/ROL-1974
 Project: Apache Roller
  Issue Type: Bug
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: David Johnson
Priority: Minor
 Fix For: 5.1


 mvn clean install of roller trunk reports these POM errors:
 Downloading: 
 http://repo.maven.apache.org/maven2/net/oauth/core/oauth/20090531/oauth-20090531.pom
 [WARNING] The POM for net.oauth.core:oauth:jar:20090531 is missing, no 
 dependency information available
 Downloading: 
 http://repo.maven.apache.org/maven2/net/oauth/core/oauth-provider/20090531/oauth-provider-20090531.pom
 [WARNING] The POM for net.oauth.core:oauth-provider:jar:20090531 is missing, 
 no dependency information available
 These 20090531 dependencies are not declared in the Roller POM but referenced 
 by Roller's Propono dependency.  Roller explicitly lists the 20100527 version 
 of the above JARs instead to override the 2009 ones.  Upgrading Propono to 
 the new 20100527 versions should cause the above error message to go away, 
 also the Roller team would no longer need to explicitly list the 2010 version 
 in its POM.
 Likewise, upgrading Propono to use the latest versions of xmlrpc-common, 
 xmlrpc-client, and ws-commons-util that Roller presently declares will allow 
 for removal of these three dependencies from our POM as well as allow us to 
 remove the exclusions for these dependencies under Roller's Propono 
 dependency: 
 http://svn.apache.org/viewvc/roller/trunk/app/pom.xml?revision=1523514view=markup#l188.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1215) Andreas08 Theme Improvements

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1215.
---


 Andreas08 Theme Improvements
 

 Key: ROL-1215
 URL: https://issues.apache.org/jira/browse/ROL-1215
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Affects Versions: 3.0
 Environment: All
Reporter: Rob Wilson
Assignee: Glen Mazza
Priority: Trivial

 The new Andreas theme does not have categories or bookmarks.  Also no 
 category feeds exist. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1974) Roller's ROME Propono dependency needs updating to use newer JARs

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1974.
---


 Roller's ROME Propono dependency needs updating to use newer JARs
 -

 Key: ROL-1974
 URL: https://issues.apache.org/jira/browse/ROL-1974
 Project: Apache Roller
  Issue Type: Bug
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: David Johnson
Priority: Minor
 Fix For: 5.1


 mvn clean install of roller trunk reports these POM errors:
 Downloading: 
 http://repo.maven.apache.org/maven2/net/oauth/core/oauth/20090531/oauth-20090531.pom
 [WARNING] The POM for net.oauth.core:oauth:jar:20090531 is missing, no 
 dependency information available
 Downloading: 
 http://repo.maven.apache.org/maven2/net/oauth/core/oauth-provider/20090531/oauth-provider-20090531.pom
 [WARNING] The POM for net.oauth.core:oauth-provider:jar:20090531 is missing, 
 no dependency information available
 These 20090531 dependencies are not declared in the Roller POM but referenced 
 by Roller's Propono dependency.  Roller explicitly lists the 20100527 version 
 of the above JARs instead to override the 2009 ones.  Upgrading Propono to 
 the new 20100527 versions should cause the above error message to go away, 
 also the Roller team would no longer need to explicitly list the 2010 version 
 in its POM.
 Likewise, upgrading Propono to use the latest versions of xmlrpc-common, 
 xmlrpc-client, and ws-commons-util that Roller presently declares will allow 
 for removal of these three dependencies from our POM as well as allow us to 
 remove the exclusions for these dependencies under Roller's Propono 
 dependency: 
 http://svn.apache.org/viewvc/roller/trunk/app/pom.xml?revision=1523514view=markup#l188.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (ROL-2039) Rename webpage and roller_templatecode tables

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-2039:


Fix Version/s: 5.1

 Rename webpage and roller_templatecode tables
 -

 Key: ROL-2039
 URL: https://issues.apache.org/jira/browse/ROL-2039
 Project: Apache Roller
  Issue Type: Task
  Components: Data Model  JPA Backend
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
 Fix For: 5.1


 Rename weblog table to custom_template and roller_templatecode to 
 custom_template_rendition  corresponding POJO change in code to better 
 clarify their purpose.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (ROL-2048) Roller needs a new logo

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110132#comment-14110132
 ] 

Glen Mazza commented on ROL-2048:
-

Paying for people to use Apache Roller is a bridge I'm personally reluctant to 
cross.  I would be happy with just a 5.1 or R for now (5.2 won't be around 
for a long time so 5.1 is OK); later fancier options can be considered.  One 
can more clearly evaluate better solutions once the current major problem 
(5.0) is removed.


 Roller needs a new logo
 ---

 Key: ROL-2048
 URL: https://issues.apache.org/jira/browse/ROL-2048
 Project: Apache Roller
  Issue Type: Task
  Components: Website and Documentation
Affects Versions: 5.1.1
Reporter: Glen Mazza
Assignee: Roller Unassigned

 The Roller logo of the steamroller with the 5.0 on the flag needs updating, 
 changing it to 5.1 or possibly to a new flag that no longer has the version 
 number on it so it will never need to be updated again.  I could imagine 
 replacing it with an R, or something without any text, perhaps some form of 
 tricolor carrying the red and tan colors of the standard Roller UI theme 
 along with the green color used to indicate the success action.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (ROL-2047) Would it be possible to add rel tag dropdown with pre-set attributes to insert/modify hyperlink window?

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14101614#comment-14101614
 ] 

Glen Mazza commented on ROL-2047:
-

Re: I am struggling to add nofollows by hand  you can also copy and paste 
the text in an standard text editor and do a global search and replace, if that 
would help.

 Would it be possible to add rel tag dropdown with pre-set attributes to 
 insert/modify hyperlink window?
 ---

 Key: ROL-2047
 URL: https://issues.apache.org/jira/browse/ROL-2047
 Project: Apache Roller
  Issue Type: Improvement
  Components: User Interface - Weblog Editor
Affects Versions: 5.0.4
 Environment: Debian/Ubuntu
Reporter: Tamas Balazs
Assignee: Roller Unassigned

 When I try to add a hyperlink to an anchor word there is only option to 
 set-up the target attribute of the HTML element. It would be good to be 
 able to add rel attribute too (tag, nofollow, bookmark, etc). I am 
 struggling to add nofollows by hand.
 Thank you
 Tamas 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Assigned] (ROL-1739) Missing constraint on weblogentrytagagg table

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza reassigned ROL-1739:
---

Assignee: Glen Mazza  (was: Roller Unassigned)

 Missing constraint on weblogentrytagagg table
 -

 Key: ROL-1739
 URL: https://issues.apache.org/jira/browse/ROL-1739
 Project: Apache Roller
  Issue Type: Bug
  Components: Data Model  JPA Backend
Reporter: David Johnson
Assignee: Glen Mazza

 from Tatsuya Noyori on the Roller user list:
 I have had an error on Roller that is caused by duplicated records on
 roller_weblogentrytagagg when I post an entry by AtomPub.
 Thus, I would like to suggest to add the following SQL to dbscript of
 create.sql in Roller.
 alter table roller_weblogentrytagagg add constraint rweta_name_uq
 unique ( websiteid, name );



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (ROL-1982) Tree View for Archives

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-1982:


Assignee: Gaurav Saini  (was: Roller Unassigned)

 Tree View for Archives
 --

 Key: ROL-1982
 URL: https://issues.apache.org/jira/browse/ROL-1982
 Project: Apache Roller
  Issue Type: New Feature
  Components: Themes and Macros
Reporter: Gaurav Saini
Assignee: Gaurav Saini
Priority: Minor
 Attachments: archiveTree.patch, archiveTree.png


 A macro that would provide the data of the Archives in Tree Structure 
 something like [1]. I think it would be a nice enhancement to Roller, as 
 Archive Pages are rarely used and this macro can be easily added to the Side 
 menu of the blog.
 [1] http://coheigea.blogspot.com/



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (ROL-1739) Missing constraint on weblogentrytagagg table

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-1739.
-

   Resolution: Fixed
Fix Version/s: 5.1

Added to createdb.vm script (for new databases) in order to trap the potential 
error in the code; not adding to the 500-to-510 migration script in case legacy 
invalid data exists in those tables.

 Missing constraint on weblogentrytagagg table
 -

 Key: ROL-1739
 URL: https://issues.apache.org/jira/browse/ROL-1739
 Project: Apache Roller
  Issue Type: Bug
  Components: Data Model  JPA Backend
Reporter: David Johnson
Assignee: Glen Mazza
 Fix For: 5.1


 from Tatsuya Noyori on the Roller user list:
 I have had an error on Roller that is caused by duplicated records on
 roller_weblogentrytagagg when I post an entry by AtomPub.
 Thus, I would like to suggest to add the following SQL to dbscript of
 create.sql in Roller.
 alter table roller_weblogentrytagagg add constraint rweta_name_uq
 unique ( websiteid, name );



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (ROL-2044) Member management page allows user to remove himself from blog.

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2044.
-

   Resolution: Fixed
Fix Version/s: 5.1

 Member management page allows user to remove himself from blog.
 ---

 Key: ROL-2044
 URL: https://issues.apache.org/jira/browse/ROL-2044
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - General
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
 Fix For: 5.1


 Despite message that it's not allowed, users can delete themselves from their 
 own blogs, as well as demote themselves.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (ROL-2043) Switch from YUI3 to JQuery UI for autocomplete, tabs, dialogs

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2043.
-

   Resolution: Fixed
Fix Version/s: 5.1

YUI3 all pulled out with the exception of css fonts/grids/reset, not available 
with JQuery.

 Switch from YUI3 to JQuery UI for autocomplete, tabs, dialogs
 -

 Key: ROL-2043
 URL: https://issues.apache.org/jira/browse/ROL-2043
 Project: Apache Roller
  Issue Type: Task
  Components: User Interface - General
Reporter: Glen Mazza
Assignee: Glen Mazza
 Fix For: 5.1


 YUI3 is proving very bloated, not available via SSL on a CDN, and responsible 
 for 1000's of Sonar complaints--switch to the more commonly used JQuery UI so 
 we can remove YUI3 from our distribution.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1107) Restriction of Blog creation

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1107.
---

Resolution: Not a Problem

Roller presently has a groupblogging.enabled property, which if set to false 
limits a user to just one blog.  That should be sufficient for most use cases.

For the other issue, of allowing users to register but not allow them to create 
a new blog, we have a setting for that too on our server administration page, 
user creation of new blogs can be disabled entirely (server setting) but still 
allowing the administrator to manually create the blogs for each user.

 Restriction of Blog creation
 

 Key: ROL-1107
 URL: https://issues.apache.org/jira/browse/ROL-1107
 Project: Apache Roller
  Issue Type: New Feature
  Components: Authentication, Roles and Access Controls
Reporter: Dave Avent
Assignee: Roller Unassigned

 A very useful feature (for multi user systems) would be the ability to 
 restrict/moderate the creation of blogs so that, just because someone is 
 registered, they don't necessarily have the ability to create a new blog.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1785) Design menu not showing when themes.customtheme.allowed=false

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1785.
---

Resolution: Later

Item from 2009.  Greg, until we get much larger I think what we presently have 
is sufficient.  If the blog admin shuts off customization of themes, he 
generally doesn't want the themes not to change, period -- which would include 
both switching the themes and altering them, so disabling the Design tab 
entirely would appear appropriate.  There's just not enough demand yet for I 
don't want the themes to be customized, but it's OK for the user to change the 
theme entirely.  Also, if we partially altered the Design tab to just allow 
theme-switching we'd also have to hide all the text implying that the theme can 
also be customized, cumbersome work to do.

 Design menu not showing when themes.customtheme.allowed=false
 -

 Key: ROL-1785
 URL: https://issues.apache.org/jira/browse/ROL-1785
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Affects Versions: 5.0
Reporter: Greg Huber
Assignee: Roller Unassigned
Priority: Minor

 In editor-menu.xml there is an option set to not show the design menu if 
 themes.customtheme.allowed is set to false.
 ie:
 enabledProperty=themes.customtheme.allowed
 This will completely disable the theme switching also.  There is a action:
 action name=themeEdit!* method={1}
 
 class=org.apache.roller.weblogger.ui.struts2.editor.ThemeEdit
 result name=input type=tiles.ThemeEdit/result
 result name=input-sharedonly 
 type=tiles.ThemeEditSharedThemesOnly/result
 /action
 that takes care of this and only allows theme switching.  I am not sure if 
 this is now what it is supposed to do ie completelt disable themes, we loose 
 functionality if it is.
 Also  .ThemeEditSharedThemesOnly is missing from tiles.xml.
 Cheers Greg



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (ROL-2044) Member management page allows user to remove himself from blog.

[Glen Mazza (JIRA)]

Glen Mazza created ROL-2044:
---

 Summary: Member management page allows user to remove himself from 
blog.
 Key: ROL-2044
 URL: https://issues.apache.org/jira/browse/ROL-2044
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - General
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Roller Unassigned


Despite message that it's not allowed, users can delete themselves from their 
own blogs, as well as demote themselves.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1993) Roller JUnit tests aren't running properly on Sonar

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1993.
---

Resolution: Cannot Reproduce

The new Sonar doesn't report back Unit Tests, seeing that as a Jenkins issue, 
so this problem has resolved itself.

However, Roller's stats have been absolutely decimated by the addition of the 
YUI3 library within its code, its RCI % fell from a very decent 90% making us 
among the better Roller apps, to a terrible 50% ranking us near the bottom.  We 
really need to switch from YUI3 to JQuery.

 Roller JUnit tests aren't running properly on Sonar
 ---

 Key: ROL-1993
 URL: https://issues.apache.org/jira/browse/ROL-1993
 Project: Apache Roller
  Issue Type: Task
  Components: Website and Documentation
Reporter: Glen Mazza
Assignee: Roller Unassigned
Priority: Minor

 Only about 20% of Roller's tests are currently passing via Sonar:
 https://analysis.apache.org/drilldown/measures/145470?metric=test_success_density
 For Sonar, the failing ones appear to be all database-related -- unsure if 
 related to the port that our in-memory Derby database uses.
 This is not a problem with JUnit tests run on Jenkins.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Comment Edited] (ROL-1993) Roller JUnit tests aren't running properly on Sonar

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14075502#comment-14075502
 ] 

Glen Mazza edited comment on ROL-1993 at 7/26/14 11:04 PM:
---

The new Sonar doesn't report back Unit Tests, seeing that as a Jenkins issue, 
so this problem has resolved itself.

However, Roller's stats have been absolutely decimated by the addition of the 
YUI3 library within its code, its RCI % fell from a very decent 90% making us 
among the better Apache apps, to a terrible 50% ranking us near the bottom.  We 
really need to switch from YUI3 to JQuery.


was (Author: gmazza):
The new Sonar doesn't report back Unit Tests, seeing that as a Jenkins issue, 
so this problem has resolved itself.

However, Roller's stats have been absolutely decimated by the addition of the 
YUI3 library within its code, its RCI % fell from a very decent 90% making us 
among the better Roller apps, to a terrible 50% ranking us near the bottom.  We 
really need to switch from YUI3 to JQuery.

 Roller JUnit tests aren't running properly on Sonar
 ---

 Key: ROL-1993
 URL: https://issues.apache.org/jira/browse/ROL-1993
 Project: Apache Roller
  Issue Type: Task
  Components: Website and Documentation
Reporter: Glen Mazza
Assignee: Roller Unassigned
Priority: Minor

 Only about 20% of Roller's tests are currently passing via Sonar:
 https://analysis.apache.org/drilldown/measures/145470?metric=test_success_density
 For Sonar, the failing ones appear to be all database-related -- unsure if 
 related to the port that our in-memory Derby database uses.
 This is not a problem with JUnit tests run on Jenkins.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1598) Trackback enhancements

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1598.
---

Resolution: Unresolved

Item from 2007.  There hasn't been enough demand to separate the comment count 
from the trackback count to make it worthwhile to implement, separate counts, 
especially as they are both comments, it's just that some choose to leave their 
comments on their own blog instead of a comment field.

For the 2nd issue, I'm not sure what the problem is, in particular the part 
cross-refer my entries from bsc/arungupta all the time -- what does 
cross-refering mean -- leaving a trackback for each blog entry on each of the 
two blogs pointing to the other?  I'm not sure what the purpose of that would 
be, at any rate though this problem should be simplified to a single blog 
either not sending trackbacks or not correctly receiving them, if that is in 
fact happening today we'll welcome a bug report over it.

 Trackback enhancements
 --

 Key: ROL-1598
 URL: https://issues.apache.org/jira/browse/ROL-1598
 Project: Apache Roller
  Issue Type: New Feature
  Components: Pings and Trackbacks
Reporter: linda skrocki
Assignee: Roller Unassigned
Priority: Minor

 Per Arun, Sun Blogger:
 1. I've around 781 comments on my blog but a sizable number of them are 
 trackbacks. Is there a way to distinguish between the number of trackbacks 
 and comments on my blog ?
 2. I always cross-post my technical posts to weblogs.java.net/blog/arungupta 
 and blogs.sun.com/arungupta and cross-refer my entries from bsc/arungupta all 
 the time. Only entries posted at java.net leave a trackback, not the ones at 
 bsc/arungupta.
 For example, look at:
 http://blogs.sun.com/arungupta/entry/mid_west_java_tech_days#comments
 The only trackback is from:
 http://weblogs.java.net/blog/arungupta/archive/2007/10/mid_west_java_t_1.html
 but none from:
 http://blogs.sun.com/arungupta/entry/mid_west_java_tech_days1 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-1990) Switch to svnpubsub for Apache releases

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1990.
---

Resolution: Fixed

According to INFRA (INFRA-8015), this task is complete.

 Switch to svnpubsub for Apache releases
 ---

 Key: ROL-1990
 URL: https://issues.apache.org/jira/browse/ROL-1990
 Project: Apache Roller
  Issue Type: Task
  Components: Website and Documentation
Reporter: Glen Mazza
Assignee: Glen Mazza
Priority: Minor

 See: 
 https://issues.apache.org/jira/browse/ROL-1989?focusedCommentId=13905391page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13905391
 Also will need to update this page:
 https://cwiki.apache.org/confluence/display/ROLLER/Release+Process



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Assigned] (ROL-2034) Hide Profile Password fields with SSO

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza reassigned ROL-2034:
---

Assignee: Glen Mazza  (was: Roller Unassigned)

 Hide Profile Password fields with SSO
 -

 Key: ROL-2034
 URL: https://issues.apache.org/jira/browse/ROL-2034
 Project: Apache Roller
  Issue Type: Improvement
  Components: User Management
Affects Versions: 5.1
Reporter: Jürgen Weber
Assignee: Glen Mazza

 With users.sso.enabled=true
 the password fields in Profile.jsp should be hidden
 Grüße aus Deutschland, Jürgen



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (ROL-2042) email and username fields from LDAP

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14073249#comment-14073249
 ] 

Glen Mazza commented on ROL-2042:
-

Awesome!  Many thanks Juergen!  I haven't forgotten the LDAP stuff but I'm 
trying to get some DB changes in for 5.1 before a necessary data model freeze 
for migration testing.  This will be looked at soon (along with the other LDAP 
issues in JIRA).

 email and username fields from LDAP
 ---

 Key: ROL-2042
 URL: https://issues.apache.org/jira/browse/ROL-2042
 Project: Apache Roller
  Issue Type: Improvement
  Components: Authentication, Roles and Access Controls
Affects Versions: 5.1
Reporter: Jürgen Weber
Assignee: Roller Unassigned
 Attachments: CustomUserRegistry.patch, LDAPUserDetails.java, 
 LDAPUserDetailsMapper.java, security.xml


 Current implementation of LDAP based Spring security does not retrieve email 
 and name attributes from LDAP.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (ROL-2030) Replace Xinha editor with something more recent

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2030.
-

   Resolution: Fixed
Fix Version/s: 5.1

Upgraded to latest Xinha 0.96.1.

 Replace Xinha editor with something more recent
 ---

 Key: ROL-2030
 URL: https://issues.apache.org/jira/browse/ROL-2030
 Project: Apache Roller
  Issue Type: Task
  Components: User Interface - Weblog Editor
Affects Versions: 5.1
Reporter: Glen Mazza
Priority: Minor
 Fix For: 5.1


 Present Xinha editor is 0.95 from 2008, 0.96.1 from 2010 is available: 
 http://trac.xinha.org/wiki/DownloadsPage.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Assigned] (ROL-1554) Listing Box Invite a new user to join... does not have a horizontal scrolling bar

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza reassigned ROL-1554:
---

Assignee: Glen Mazza  (was: Roller Unassigned)

 Listing Box Invite a new user to join... does not have a horizontal 
 scrolling bar
 ---

 Key: ROL-1554
 URL: https://issues.apache.org/jira/browse/ROL-1554
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - Weblog Editor
Affects Versions: 4.0
 Environment: glassfish - winXP
Reporter: Davis Nguyen
Assignee: Glen Mazza

 The Listing Box Invite a new user to join this weblog does not have a 
 horizontal scrolling bar
 STEPS TO REPRODUCE:
 1. Install Glassfish V2 server build 58c
 2. Install Roller M1 b04 build
 3. Start Roller  Register an admin user  create a Weblog and a web log entry
 4. Register another user as listed below:
  Username:  ThisIsATestForGroupBlog
  Password: test
  Password (confirm) test
 Screen name: grouptest
 Full Name: Group Test
 Email: glassfish.apache.roller.java@sun.com
 5. Go to Preferences tab  Members  Invite New Member 
 BUG:
  Can not view the user ThisIsATestForGroupBlog email alias
 




--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (ROL-1554) Listing Box Invite a new user to join... does not have a horizontal scrolling bar

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-1554.
-

Resolution: Fixed

Difficult to activate horizontal scrollbar as data is populated via Ajax; 
however, I expanded its width 25% to cover all but the longest possible names 
and email addresses.

 Listing Box Invite a new user to join... does not have a horizontal 
 scrolling bar
 ---

 Key: ROL-1554
 URL: https://issues.apache.org/jira/browse/ROL-1554
 Project: Apache Roller
  Issue Type: Bug
  Components: User Interface - Weblog Editor
Affects Versions: 4.0
 Environment: glassfish - winXP
Reporter: Davis Nguyen
Assignee: Glen Mazza

 The Listing Box Invite a new user to join this weblog does not have a 
 horizontal scrolling bar
 STEPS TO REPRODUCE:
 1. Install Glassfish V2 server build 58c
 2. Install Roller M1 b04 build
 3. Start Roller  Register an admin user  create a Weblog and a web log entry
 4. Register another user as listed below:
  Username:  ThisIsATestForGroupBlog
  Password: test
  Password (confirm) test
 Screen name: grouptest
 Full Name: Group Test
 Email: glassfish.apache.roller.java@sun.com
 5. Go to Preferences tab  Members  Invite New Member 
 BUG:
  Can not view the user ThisIsATestForGroupBlog email alias
 




--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Assigned] (ROL-2030) Update Xinha editor

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza reassigned ROL-2030:
---

Assignee: Glen Mazza  (was: Roller Unassigned)

 Update Xinha editor
 ---

 Key: ROL-2030
 URL: https://issues.apache.org/jira/browse/ROL-2030
 Project: Apache Roller
  Issue Type: Task
  Components: User Interface - Weblog Editor
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
Priority: Minor

 Present Xinha editor is 0.95 from 2008, 0.96.1 from 2010 is available: 
 http://trac.xinha.org/wiki/DownloadsPage.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (ROL-2030) Update Xinha editor

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069340#comment-14069340
 ] 

Glen Mazza commented on ROL-2030:
-

The Xinha download page isn't working, at least for downloading the latest 
0.96.1.  It hasn't been updated since 2010 anyway.

CKEditor appears to be the main RTE today, however it is Mozilla Public License 
(weak-copyleft), which Apache requires that we distribute only in binary form 
if we're to use it:
http://www.apache.org/legal/resolved.html#category-b.  However CKEditor is 
virtually all JavaScript and hence must be distributed in source form, i.e., we 
can't use it.

A few forks of wysihtml5 (https://github.com/schnawel007/bootstrap3-wysihtml5, 
https://github.com/Waxolunist/bootstrap3-wysihtml5-bower, 
http://jhollingworth.github.io/bootstrap-wysihtml5/) use an Apache-friendly 
license (MIT) and modern technologies, even if supported only by a few people.  
As of now, that may be the best/only alternative for us if we wish to update 
Xinha.

 Update Xinha editor
 ---

 Key: ROL-2030
 URL: https://issues.apache.org/jira/browse/ROL-2030
 Project: Apache Roller
  Issue Type: Task
  Components: User Interface - Weblog Editor
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
Priority: Minor

 Present Xinha editor is 0.95 from 2008, 0.96.1 from 2010 is available: 
 http://trac.xinha.org/wiki/DownloadsPage.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (ROL-2030) Replace Xinha editor with something more recent

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza updated ROL-2030:


Assignee: (was: Glen Mazza)

 Replace Xinha editor with something more recent
 ---

 Key: ROL-2030
 URL: https://issues.apache.org/jira/browse/ROL-2030
 Project: Apache Roller
  Issue Type: Task
  Components: User Interface - Weblog Editor
Affects Versions: 5.1
Reporter: Glen Mazza
Priority: Minor

 Present Xinha editor is 0.95 from 2008, 0.96.1 from 2010 is available: 
 http://trac.xinha.org/wiki/DownloadsPage.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Comment Edited] (ROL-2030) Replace Xinha editor with something more recent

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069340#comment-14069340
 ] 

Glen Mazza edited comment on ROL-2030 at 7/22/14 12:24 AM:
---

The Xinha download page isn't working, at least for downloading the latest 
0.96.1.

CKEditor appears to be the main RTE today, however it is Mozilla Public License 
(weak-copyleft), which Apache requires that we distribute only in binary form 
if we're to use it:
http://www.apache.org/legal/resolved.html#category-b.  However CKEditor is 
virtually all JavaScript and hence must be distributed in source form, i.e., we 
can't use it.

A few forks of wysihtml5 (https://github.com/schnawel007/bootstrap3-wysihtml5, 
https://github.com/Waxolunist/bootstrap3-wysihtml5-bower, 
http://jhollingworth.github.io/bootstrap-wysihtml5/) use an Apache-friendly 
license (MIT) and modern technologies, even if supported only by a few people.  
As of now, that may be the best/only alternative for us if we wish to update 
Xinha.


was (Author: gmazza):
The Xinha download page isn't working, at least for downloading the latest 
0.96.1.  It hasn't been updated since 2010 anyway.

CKEditor appears to be the main RTE today, however it is Mozilla Public License 
(weak-copyleft), which Apache requires that we distribute only in binary form 
if we're to use it:
http://www.apache.org/legal/resolved.html#category-b.  However CKEditor is 
virtually all JavaScript and hence must be distributed in source form, i.e., we 
can't use it.

A few forks of wysihtml5 (https://github.com/schnawel007/bootstrap3-wysihtml5, 
https://github.com/Waxolunist/bootstrap3-wysihtml5-bower, 
http://jhollingworth.github.io/bootstrap-wysihtml5/) use an Apache-friendly 
license (MIT) and modern technologies, even if supported only by a few people.  
As of now, that may be the best/only alternative for us if we wish to update 
Xinha.

 Replace Xinha editor with something more recent
 ---

 Key: ROL-2030
 URL: https://issues.apache.org/jira/browse/ROL-2030
 Project: Apache Roller
  Issue Type: Task
  Components: User Interface - Weblog Editor
Affects Versions: 5.1
Reporter: Glen Mazza
Priority: Minor

 Present Xinha editor is 0.95 from 2008, 0.96.1 from 2010 is available: 
 http://trac.xinha.org/wiki/DownloadsPage.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (ROL-2030) Replace Xinha editor with something more recent

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069582#comment-14069582
 ] 

Glen Mazza commented on ROL-2030:
-

Actually, spoke with James of the Xinha team -- he said it's common to just 
pull the latest SVN version (which has had some updates since its last 2010 
release).

 Replace Xinha editor with something more recent
 ---

 Key: ROL-2030
 URL: https://issues.apache.org/jira/browse/ROL-2030
 Project: Apache Roller
  Issue Type: Task
  Components: User Interface - Weblog Editor
Affects Versions: 5.1
Reporter: Glen Mazza
Priority: Minor

 Present Xinha editor is 0.95 from 2008, 0.96.1 from 2010 is available: 
 http://trac.xinha.org/wiki/DownloadsPage.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Closed] (ROL-2025) No apparent algorithm as to why custom theme files are marked deletable.

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-2025.
---

Resolution: Not a Problem

WeblogTemplate defines Weblog and _day templates as required in cases where 
a custom theme is being used.

 No apparent algorithm as to why custom theme files are marked deletable.
 

 Key: ROL-2025
 URL: https://issues.apache.org/jira/browse/ROL-2025
 Project: Apache Roller
  Issue Type: Bug
  Components: Themes and Macros
Reporter: Glen Mazza
Assignee: Roller Unassigned

 On the theme customization file list page, there is one column which 
 identifies whether a resource file can be deleted or not.  Does not appear to 
 follow any useful pattern about why some can be deleted and others not.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (ROL-2039) Rename webpage and roller_templatecode tables

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2039.
-

Resolution: Fixed

Fixed, and tested on Derby DB that it works during the 5.0.4 - 5.1 upgrade.

 Rename webpage and roller_templatecode tables
 -

 Key: ROL-2039
 URL: https://issues.apache.org/jira/browse/ROL-2039
 Project: Apache Roller
  Issue Type: Task
  Components: Data Model  JPA Backend
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza

 Rename weblog table to custom_template and roller_templatecode to 
 custom_template_rendition  corresponding POJO change in code to better 
 clarify their purpose.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (ROL-2033) Test Roller 5.1 with a weblog client

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14067781#comment-14067781
 ] 

Glen Mazza commented on ROL-2033:
-

If you can confirm some Swedish/German/French funny characters also work with 
that weblog client, we can also close 
https://issues.apache.org/jira/browse/ROL-1118 as a Can't Reproduce.  We 
don't need to chase a 2006 issue that thoroughly if it works today with a basic 
client.

 Test Roller 5.1 with a weblog client
 

 Key: ROL-2033
 URL: https://issues.apache.org/jira/browse/ROL-2033
 Project: Apache Roller
  Issue Type: Test
  Components: Web Services
Affects Versions: 5.1
Reporter: David Johnson
Assignee: David Johnson

 Test Roller 5.1's MetaWeblog API and Atom Protocol support with at least one 
 weblog client.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (ROL-2041) gaurav theme -- render full blog entries on main blog page if no summary given

[Glen Mazza (JIRA)]

Glen Mazza created ROL-2041:
---

 Summary: gaurav theme -- render full blog entries on main blog 
page if no summary given
 Key: ROL-2041
 URL: https://issues.apache.org/jira/browse/ROL-2041
 Project: Apache Roller
  Issue Type: Improvement
  Components: Themes and Macros
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Gaurav Saini


Per discussion on mailing list, for any blog entry lacking a summary, to render 
the full blog entry within the gaurav theme as currently done with the other 
themes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (ROL-2022) Add Categories, demote tags from gaurav theme

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2022.
-

   Resolution: Fixed
Fix Version/s: 5.1

Gaurav stated earlier he is finished with this issue.  [~gauravsaini03] you do 
have the Resolve and Close buttons available after logging into JIRA, 
right?  I want to make sure you have the permissions you need to close issues.

 Add Categories, demote tags from gaurav theme
 -

 Key: ROL-2022
 URL: https://issues.apache.org/jira/browse/ROL-2022
 Project: Apache Roller
  Issue Type: Task
  Components: Themes and Macros
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Gaurav Saini
 Fix For: 5.1


 The gaurav theme shows a hot tags listing the top 30 tags, which doesn't 
 look good if the blogger has just started out with a few blogs (or is not 
 even using tags.)  Either remove the hot tags and put something else there, 
 or only show the tags once a certain number has been used by the blog.
 Also, Roller provides weblog categories, add a category listing to the blog 
 by default.  If the blogger doesn't use categories, he can get them removed 
 from his copy of the theme.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (ROL-2019) Upgrade the Yahoo User Interface (YUI) library provided by Roller.

[Glen Mazza (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ROL-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza resolved ROL-2019.
-

   Resolution: Fixed
Fix Version/s: 5.1

All YUI2 has been ripped out.  Roller UI and Fauxcoly using latest release YUI 
3.17.2.

 Upgrade the Yahoo User Interface (YUI) library provided by Roller.
 --

 Key: ROL-2019
 URL: https://issues.apache.org/jira/browse/ROL-2019
 Project: Apache Roller
  Issue Type: Task
  Components: Themes and Macros
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Glen Mazza
 Fix For: 5.1


 The YUI component library used by the Fauxcoly theme and available for other 
 themes, kept in webapp/roller-ui/yui is from 2009.  Replace it with a modern 
 release of YUI and make sure Fauxcoly still works with it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (ROL-2022) Add Categories, demote tags from gaurav theme

[Glen Mazza (JIRA)]

[ 
https://issues.apache.org/jira/browse/ROL-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14063569#comment-14063569
 ] 

Glen Mazza commented on ROL-2022:
-

Hi Gaurav, I'm looking at getPopularTags() right now (good for both gaurav and 
fauxcoly fonts.)

I noticed a problem with the category drop-down.  Roller requires a minimum of 
one category.  If a blogger just keeps one category (deletes the other two 
default ones), it is equivalent to saying he doesn't want to have his blog 
entries separated by categories (maybe he doesn't blog often enough or about 
different topics in order to need different categories, or otherwise prefers to 
distinguish his articles using tags.)  In that case, the theme should not have 
a Category drop down appear.  Can you have the Category drop-down disappear in 
cases where the blogger has fewer than two categories?  Thanks!

 Add Categories, demote tags from gaurav theme
 -

 Key: ROL-2022
 URL: https://issues.apache.org/jira/browse/ROL-2022
 Project: Apache Roller
  Issue Type: Task
  Components: Themes and Macros
Affects Versions: 5.1
Reporter: Glen Mazza
Assignee: Gaurav Saini

 The gaurav theme shows a hot tags listing the top 30 tags, which doesn't 
 look good if the blogger has just started out with a few blogs (or is not 
 even using tags.)  Either remove the hot tags and put something else there, 
 or only show the tags once a certain number has been used by the blog.
 Also, Roller provides weblog categories, add a category listing to the blog 
 by default.  If the blogger doesn't use categories, he can get them removed 
 from his copy of the theme.



--
This message was sent by Atlassian JIRA
(v6.2#6252)