nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

new date type on HEAD version??

tiofelix

I download the last code from the web site http://www.alfresco.org/alfresco/HEAD with snv, something changes about –>

          
<import uri="http://www.alfresco.org/model/dictionary/1.0" prefix="d"/>
  …
<type…>
   …
  <properties>
        …
      <property name="my:dataen">
            <type>d:date</type>
      </property>
  </properties>
</type>
‍‍‍‍‍‍‍‍‍‍‍‍‍

but now these properties can not be showed… "None" appears.

Find more posts tagged with

Comments

tiofelix

And this warning????

2006-09-05 10:07:43,796 WARN [org.hibernate.cache.ReadWriteCache] An item was expired by the cache while it was locked (increase your cache timeout): org.alfresco.repo.domain.hibernate.NodeImpl.parentAssocs#409

gavinc

The date picker renderer has changed to allow dates to be set back to "None". Now when a date property has null in the database "None" is shown in the UI (showing today's date when null was in the database is a bug).

The "None" text can be clicked on to set the date to today's date (unless the propery in question is protected, in which case the property will be shown in a gray italic font). There are now also buttons available to set the date back to null and to go to today's date.

kevinr

And this warning????

2006-09-05 10:07:43,796 WARN [org.hibernate.cache.ReadWriteCache] An item was expired by the cache while it was locked (increase your cache timeout): org.alfresco.repo.domain.hibernate.NodeImpl.parentAssocs#409

This warning should not cause a problem but needs to be fixed - i've raised a JIRA issue here:
http://issues.alfresco.com/browse/AR-833

Thanks,

Kevin

paulhh

I believe the fix has been checked in now.

Paul.

tiofelix

The date picker renderer has changed to allow dates to be set back to "None". Now when a date property has null in the database "None" is shown in the UI (showing today's date when null was in the database is a bug).

The "None" text can be clicked on to set the date to today's date (unless the propery in question is protected, in which case the property will be shown in a gray italic font). There are now also buttons available to set the date back to null and to go to today's date.

Hi Gavin,

there is some patch for alfresco 1.3 release to give the same funcionality?? or some try some way to show "none" instead of showing today's date. Now i would like to create a property "delivery date" and user don't know at the time this date. Thanks Gavin.

Regards,

gavinc

There isn't a patch for this fix for 1.3 and as far as I know there currently aren't any plans to do so.

You maybe able to do it yourself by retrofitting org.alfresco.web.ui.common.renderer.DatePickerRenderer from 1.4 into 1.3.

tiofelix

There is some way to configure the new DatePickerRenderer to show today's date by default?? Because i want some d:date propertys to be shown with "none" and others with today's date.

Thanks.

gavinc

Hi,

Yes, there is.

There's a property that can be set on DatePickerGenerator and DateTimePickerGenerator called "initialiseIfNull". If this is set to true then the date picker will render today's date (like in previous versions).

Have a look at faces-config-beans.xml to see an example of how you set it, it's commented out by default. Have a look at http://wiki.alfresco.com/wiki/Simple_Customisations#Resetting_Date_Picker_Behaviour for more info.

tiofelix

Ok, I know that, but the problem is if you want d:date propertys to be shown with "none" and others with today's date by default.

gavinc

Then you create a copy of the DatePickerRenderer in faces-config-beans.xml and place it in your faces config file and give it a different name i.e. MyDatePickerRenderer.

Then in the property config for those properties that you want to have today's date use component-generator="MyDatePickerRenderer" and for those that need "None" just leave them as is and they will default to the standard DatePickerRenderer.

tiofelix

Ok Gavin, but i don't have to create another DatePickerGenerator too??

Thanks.

gavinc

No, you don't need to implement another component generator you just have to copy the configuration which will create a new instance of the component generator. For example you would end up with:

<managed-bean>
   <managed-bean-name>DatePickerGenerator</managed-bean-name>
   <managed-bean-class>org.alfresco.web.bean.generator.DatePickerGenerator</managed-bean-class>
   <managed-bean-scope>request</managed-bean-scope>
</managed-bean>

<managed-bean>
   <managed-bean-name>TodayDatePickerGenerator</managed-bean-name>
   <managed-bean-class>org.alfresco.web.bean.generator.DatePickerGenerator</managed-bean-class>
   <managed-bean-scope>request</managed-bean-scope>
   <managed-property>
      <property-name>initialiseIfNull</property-name>
      <value>true</value>
   </managed-property>
</managed-bean>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

You can then have 2 date properties that behave differently:

<show-property name="my:todayDate" component-generator="TodayDatePickerGenerator" />

<show-property name="my:noneDate" />‍‍‍