On 08/21/2014 05:39 AM, Greg Huber wrote:
Glen,
On upgrading/testing.
##
One of my databases failed on this statement on the upgrade. The index did
not exist.
ALTER TABLE bookmark_folder DROP INDEX folder_namefolderid_uq;
Its does mention it may not exist.
Hi Greg, yes, I put a change in the code for dropping of nonexistent
indexes to be a non-fatal upgrade error, seeing that we don't need to
fail if we're trying to delete something that already doesn't exist.
Some roller installs have indexes that others don't, and I just want the
upgrade to proceed in those cases, rather than leave people with a
half-completed database.
http://svn.apache.org/viewvc/roller/trunk/app/src/main/java/org/apache/roller/weblogger/business/startup/SQLScriptRunner.java?r1=1580425&r2=1613234&diff_format=h
##
Formatting section on preference | settings
Not sure on this now, maybe needs to be removed from WeblogConfig.jsp as
bean.defaultPluginsArray has been removed.
<s:if test="!pluginsList.isEmpty">
<tr>
<td class="label"><s:text name="websiteSettings.label1" /> <br
/><s:text name="websiteSettings.label2" /></td>
<td class="field">
<s:checkboxlist theme="roller" list="pluginsList"
name="bean.defaultPluginsArray" listKey="name" listValue="name" />
</td>
<td class="description"><%-- <s:text
name="websiteSettings.tip." /> --%></td>
</tr>
</s:if>
<s:else>
<s:hidden name="defaultPlugins" />
</s:else>
My error, I should not have removed defaultPlugins from the Weblog
class, in my email of July 23rd I recommended its removal without
realizing it was indeed configurable at the blog level:
8.) defaultplugins: Always null, no place to configure at the
blog-level, as with #2 above, perhaps best to let the blog admin
configure this for all bloggers in the roller-custom.properties file.
I'll put this back in and come up with another RC3 today.
Regards,
Glen
