Which version or fork of Mayan are you using? This error is typical of
MySQL when indexing text fields. Mayan doesn't index text fields. All
indexed fields are of CHAR 255 type.
On Tuesday, July 17, 2018 at 8:40:05 AM UTC-4, vsolvs...@gmail.com wrote:
>
> I configured project using Django
We've been testing ideas for something like this. Unfortunately it would
only work once the document is uploaded and available in the system. This
is because during the upload wizard the document still doesn't exist and
cannot be referenced by a template variable like {{ document...}}.
Makes sense to filter documents. An ideal solution would be to correlation
the OS username to a Mayan user to inherit the permission. Or in the mean
time a filtering method via the mountindex command line to avoid needing to
change the code. Your question brings an interesting proposition to
We are working on adding and official method to convert the database use
from SQLite to another like Postgres. Some changes already made it to the
next version branch and we've execute successful migrations with some large
document databases.
We have included a "convertdb" command
Autocomplete is possible but will require a new API to return the top
result values so that a smart widget like Select2 could display them.
Possible but requires code changes.
What do you mean by "change the field labels"? Can you expand on this? This
one might be simpler to implement.
On
This is an interesting concept. Since Mayan was originally made to be used
in government and legal setting, one of the philosophies was to keep the
uploaded document intact. This is to preserve the chain of evidence.
In this case the possible solution we've come up with is to add new
workflow
Indeed. The documentation will be updated to specify Ubuntu 18.04. The
previous 16,04 LTS version works but the old location of the GPG binary
must be specified via SIGNATURES_GPG_PATH variable.
On Thursday, July 26, 2018 at 9:34:27 AM UTC-4, Adam Kaney wrote:
>
> I tried doing this and ran
Try adding an empty __init__.py to mayan.media and to
mayan.media.mayan_settings so that mysetting is importable
You can use the touch command:
touch /opt/mayan-edms/mayan/media/__init__.py
touch /opt/mayan-edms/mayan/media/mayan_settings/__init__.py
If you installed version 3.0, the
This was most likely caused by the automatic orientation detection. This
feature now defaults to disable since PDF are not always compliant. In 3.0
it is possible to select all the document in a page (40) and delete the
transformations. A entry can be added to the "Tools" menu to clear all
The first one is already in the published pending work list. And should be
straight forward. Might be able to push it up to add in the next release.
The second one is harder. Right now the worflow doesn't have support for
user input during execution. This is something we want to add but
Thanks. Your idea seem to do the what is expected but has the following
major drawbacks:
- Creating a new doc will destroy the link between the "source" and the
created PDF
- By deleting the original document, we can no longer have access to the
source. This is problematic for the review
I have configured mayanedms in ubuntu 16 successfully . But when i tried
uploading document , document not saved in media folder. I have configured
redis too .Can you help me solve this error
On Thursday, July 26, 2018 at 2:40:23 PM UTC+5:30, vsol...@gmail.com wrote:
>
> Hi,
>
> I am trying to
Hey guys,
is there any way to use a document's metadata (I added a metadata field for
suppliers) for renaming documents via quick label? I tried it with {{
document.metadata_value_of.supplier }} with supplier being my metadata
field. Unfortunately it takes {{
13 matches
Mail list logo
