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.

2.9B troubles with forms renditions

anthonys

XML schema does not visualised with few data types,
for example it does not work with xs:date

Find more posts tagged with

Comments

pmonks

The list of supported XML Schema data types is in the Forms Developer Guide, which lives at http://wiki.alfresco.com/wiki/Forms_Developer_Guide#Overview_of_supported_XML_Schema_structures_and_data_types.

xs:date is one of the supported types and should work on the 2.9 beta, unless there's been an unintended regression. Can you post your schema (or a small sample that reproduces the problem) here?

anthonys

Ok.
For example, I'll use this sample.xsd :
<?xml version="1.0" encoding="utf-8"?>
<xs:schema elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="testForm">
    <xs:complexType>
      <xs:sequence>
        <xs:element maxOccurs="unbounded" name="eventField" type="xs:date" />
      </xs:sequence>
    </xs:complexType>
</xs:element>
</xs:schema>

After all desired uploads I'll try to fill it, but could not see any xforms widgets.
In browser error console (Mozilla FF) i can see something like this:
[Exception… "'Error: dojo.date.format: invalid pattern char: jj.nn.aa' when calling method: [nsIOnReadyStateChangeHandler::handleEvent]" nsresult: "0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)" location: "<unknown>" data: no]
and
Error: unable to find trigger insert, properties [object Object] for repeat_0
Source: http://localhost:8080/alfresco/scripts/ajax/xforms.js
Line: 3216

I've seen few other bugs with Internet Explorer 6
Radiobuttons can't change its states…

I'd like to know what is the target client browser for Alfresco?

jgrocha

I'm unable to fill the 'Press Release Form' of the demo.

I've the following error in Firefox 3.0.3/Alfresco Labs 3:

Erro: [Exception… "'Error: unable to find node C81-content' when calling method: [nsIDOMEventListener::handleEvent]"  nsresult: "0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)"  location: "<unknown>"  data: no]‍

The corresponding schema of the mentioned form is Alfresco/extras/wcm/forms/press-release.xsd

Besides this error, editing is almost impossible: the buttons related with add or remove itens in lists do not work (although something happens).
More are more errors are reported in the Firefox console.

The following errors are just a sample of the reported ones:

Erro: dojo.date.fromRfc3339 is not a function
Ficheiro de origem: http://localhost:8080/alfresco/scripts/ajax/xforms.js
Linha: 1649

Erro: unable to find trigger delete, properties [object Object] for repeat_0
Ficheiro de origem: http://localhost:8080/alfresco/scripts/ajax/xforms.js
Linha: 3224‍‍‍‍‍‍‍

There also additionaly CSS errors, like:

Aviso: Erro ao interpretar o valor da propriedade 'vertical-align'.  Declaração ignorada.
Ficheiro de origem: http://localhost:8080/alfresco/css/main.css
Linha: 212

Aviso: Esperado uma declaração mas encontrado '*'.  Ignorado para a próxima declaração.
Ficheiro de origem: http://localhost:8080/alfresco/css/picker.css
Linha: 62‍‍‍‍‍‍‍

I've already checked the limitations related with XML support, but I thought the demo schema would be supported. It isn't?

pmonks

The symptoms you describe indicate a more fundamental problem - the CSS and JS files required by Alfresco are not being loaded correctly by your browser.

There are numerous possible explanations for this, but a few things I'd suggest you check:

Those files exist in the exploded Alfresco webapp directory (${ALFRESCO_HOME}/tomcat/webapps/alfresco)
Your browser cache isn't corrupt
You're able to retrieve those files directly via your browser, and the content looks correct (ie. isn't prematurely terminated, etc.)

Cheers,
Peter