One thing you can check is datavalue table.
When you upgrade to 2.14, new column with the name
*attributeoptioncomboid *will
be created in datavalue table and it will populated with 0 by default. So
you may run query to change this value from 0 to default
categoryoptioncomboid (most of the cases
yes in mysql when we converted from 2.12 to 2.14 it doesn't work, I
manually executed update query.
On Thu, Mar 27, 2014 at 2:13 PM, Lars Helge Ă˜verland larshe...@gmail.comwrote:
On Mar 27, 2014 7:41 AM, Bharath chbhara...@gmail.com wrote:
One thing you can check is datavalue table.
On Mar 27, 2014 7:41 AM, Bharath chbhara...@gmail.com wrote:
One thing you can check is datavalue table.
When you upgrade to 2.14, new column with the name attributeoptioncomboid
will be created in datavalue table and it will populated with 0 by default.
So you may run query to change this
Hi Marcio,
The only way we can really help you is if you can include a copy of the
logs from Tomcat when the exception occurs.I have upgraded from 2.10 to
2.14 directly, so it can be done. However, there were some issues related
to duplicate orgunit groups which were very difficult to track down.
4 matches
Mail list logo