Previously metadata could be added,edited and removed to any document anytime. In recent versions, metadata types are linked to document types either are optional or required. When a metadata type is added to a document as required, that metadata MUST have a value, when it is optional, the value can be left blank. The error you are getting means that the document to which you are trying to add a metadata value doesn't has any metadata types setup up to its own document type. Go to "Setup" - > "Document types", choose a type and set the metadata type you are trying to set as either "Required" or "Optional".
On Monday, June 1, 2015 at 10:13:46 AM UTC-4, Gabriel Diteko wrote: > > Hi guys. Glory to God I have got it working well and have even deployed it > on apache2. Once you begin to understand where things are, things work out. > Thanks for all your help fellas. > > I do still have one issue though. When trying to edit metadata of > previously uploaded files, I get this error: Error editing metadata for > document GP09084.pdf; Metadata type is not valid for this document type.. > > Please advise. > > > > On Thursday, May 28, 2015 at 4:54:01 AM UTC+2, Roberto Rosario wrote: >> >> Hi Gabriel, >> >> At the end of each release notes file ( >> http://mayan.readthedocs.org/en/latest/releases/index.html) there is a >> section called "Upgrading from a previous version" ( >> http://mayan.readthedocs.org/en/latest/releases/0.13.html#upgrading-from-a-previous-version, >> >> >> http://mayan.readthedocs.org/en/latest/releases/1.0.html#upgrading-from-a-previous-version, >> >> >> http://mayan.readthedocs.org/en/latest/releases/1.1.html#upgrading-from-a-previous-version, >> >> >> http://mayan.readthedocs.org/en/latest/releases/1.1.1.html#upgrading-from-a-previous-version) >> >> perform these in order to upgrade 0.13 -> 1.0, 1.0 -> 1.1, 1.1 -> .1.1.1 >> >> You can definitely try to install the latest version and run the >> migrations for each app my hand to increase the changes of a success >> database migration. We have taken many steps to try to avoid migrations to >> fail and test against the major DBs, but this is something that can't be >> done 100% bulletproof. Make sure to backup your database before doing so >> and be ready to type SQL statements in the event some migration fail for >> whatever reason (OS, DB manager version, DB table types). In the event of >> failed migrations South will provide SQL statements in the console it >> believes will fix the problem, sometime these work, sometimes they don't. >> >> If you go this route my recommendation is to migrate each app separately: >> >> mayan-edms migrate --list >> >> will show all apps and the migration they are at. >> >> mayan-edms migrate <app name> >> >> will migrate that app to the latest migration for the release. If a >> migration fails, try the SQL statement provided. If the SQL fails, restore >> the database, migrate the app up to the one that failed and migrate another >> one instead, then continue with the one that failed in the last run. App >> migrations have dependencies coded in them so if a migration is dependent >> on another migration, it will try to migration the dependency first. >> >> The document_storate and gpg_home folders can be copied as is, there >> format of these directories and files doesn't change. There is no need to >> copy the image_cache folder, in fact I would recommend you didn't so >> that the master image for each document is created from scratch. >> >> Without actually login into your system and seeing your environment setup >> this is as explicit an upgrade procedure can get. >> >> When you say that the search link is broken, what do you mean? What is >> the error message? >> >> If your installation of Mayan EDMS is mission critical you should >> consider purchasing a support package from one of the many companies that >> provide them: http://www.mayan-edms.com/support, to reduce the risk of >> data loss or downtime. >> >> >> >> On Tuesday, May 26, 2015 at 10:50:17 AM UTC-4, Gabriel Diteko wrote: >>> >>> Hi guys. >>> >>> I am a django newbie. I have been trying to upgrade mayan from 0.13 to >>> 1.1.1 but struggling. I managed to get everything to version 1.0 but the >>> search link is broken. This project needs to be done by weeks end. My boss >>> is getting anxious. What are the ramifications of just installing a >>> completely new version of mayan and then just importing the old document >>> storage, image cache and gpg_home? Or is there maybe some very detailed >>> upgrade instructions somewhere for newbies like me? >>> >> -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
