Anyone else getting the below errors when trying to delete documents or
empty the trash?
It was definitely working on 2.7.3 release.
Thanks
CSRF verification failed. Request aborted.
More information is available with DEBUG=True.
--
**CONFIDENTIALITY
NOTICE:* *
*This transmission may
Hi - I have enabled HTTPS/SSL via Nginx after setup following the advanced
deployment guide for Nginx here.
https://mayan.readthedocs.io/en/stable/topics/deploying.html
Just modify the mayan Nginx config file as below, edit for your instance
and of course obtain a SSL certificate.
*Roberto *-
Must be a bug since moving to cabinets. I believe I had restrictions on
folders in the past.
--
**CONFIDENTIALITY
NOTICE:* *
*This transmission may contain information
which is Vimo, Inc. (DBA
Getinsured) confidential and/or legally
privileged. The information is intended
only for the
Yes - this is possible at the top level cabinet with ACL permissions set on
the cabinet. You will have to create top level cabinets per department
and then set ACL permissions on department roles you define. RIght now
there is no sub-cabinet "drawer" level permission ACLs, just for the
Hi Roberto,
As a new feature request, would be nice to use pdftk opensource tool with
command line option to rotate any PDFs that come in sideways.
Right now I have to download the document version, run pdftk command like
below and upload the output PDF as a new version for parsing and OCR
Thanks Roberto, great to have you back online.
It works as expected!
Now any way to set the message header type variable for Django, html_message,
so that the message body content is flagged as fancy HTML code and not just
plain text?
Victor
--
**CONFIDENTIALITY
NOTICE:* *
*This
I was searching for a way to change the default email template used for
emailing a link or document?
Don't seem to be able to find in the DB or on disk. Can I get the
location of this file(s).
thanks!
--
**CONFIDENTIALITY
NOTICE:* *
*This transmission may contain information
which is
Is there a way to reset this view to exclude duplicates with zero
duplicates after cleanup?
They still seem to be picked up by the search and displayed.
Thanks for all the hard work! 3.02 is a big jump forward.
--
*CONFIDENTIALITY NOTICE: *
*This transmission may contain information
and delete it from the UI.
> - Execute "touch
> /usr/share/mayan-edms/local/lib/python2.7/site-packages/mayan/media/document_storage/a5985893-a3c5-47f0-8b8c-12bbb889b99f"
>
> to create a blank file and allow the performupgrade command to finish.
>
> On Friday, March 23,
el Price wrote:
>
> Django migration squashing feature made a mess of things. I managed to
> track down the issue. Uploaded version 3.0.2. Give it a go.
>
> On Thursday, March 22, 2018 at 11:43:12 AM UTC-4, Victor Zele wrote:
>>
>> I am using PIP to install/update, not th
To migrate a specific migration of an app the command is:
>>
>> mayan-edms.py migrate events 0004
>>
>> On Thursday, March 22, 2018 at 3:56:13 AM UTC-4, Michael Price wrote:
>>>
>>> Hi! Thanks for reporting this. I've started working on fixing this
>>>
the event migration files to load first???
thanks!
On Wednesday, March 21, 2018 at 9:04:13 AM UTC-7, Victor Zele wrote:
>
> I get the below error trying to update my database from 2.7.3 to 3.0.
>
> Any ideas what to check?
>
>
> (mayan-edms) root@sjc1-mayan01:/usr/share/maya
I get the below error trying to update my database from 2.7.3 to 3.0.
Any ideas what to check?
(mayan-edms) root@sjc1-mayan01:/usr/share/mayan-edms# mayan-edms.py
performupgrade
No handlers could be found for logger "pyocr.libtesseract"
CommandError: Error during pre_upgrade signal: Migration
Found my answer on the roadmap page for workflow notifications, etc.
http://docs.mayan-edms.com/en/latest/topics/roadmap.html
--
*CONFIDENTIALITY NOTICE: *
*This transmission may contain information which is Vimo, Inc. (DBA
Getinsured) confidential and/or legally privileged. The
Found this Chrome extension to workaround the check all/none on a web
page. Seems to work fine on the Mayan search results page.
https://chrome.google.com/webstore/detail/click-all-checkboxes/fhlogpdbadmjfpndmaijnibflgnbnhof
On Tuesday, December 12, 2017 at 1:31:03 PM UTC-8, kwetiawz wrote:
On your install, go to System Menu -> Tools -> API Documentation.
On Friday, November 17, 2017 at 4:34:31 AM UTC-8, Peter Enoksson wrote:
>
> Hello,
>
> Do anybody know where to find dokumentation about the Mayan REST API?
>
> Kind regards,
> Peter
>
--
*CONFIDENTIALITY NOTICE: *
*This
I am playing around with workflows for our accounting department.
It would be nice if there was a mail action to send a notification with
document link/template to approvers when a document enters the approval
phase, etc.
For now we are playing around with the POST URL action to see if we can
Found this Chrome extension to workaround the check all/none on a web
page. Seems to work fine on the Mayan search results page.
https://chrome.google.com/webstore/detail/click-all-checkboxes/fhlogpdbadmjfpndmaijnibflgnbnhof
--
*CONFIDENTIALITY NOTICE: *
*This transmission may contain
I also noticed this as well, and would like to switch to a list view
again. Also, it would be nice to have a select all/none button on the
search results to make acting on the results much easier than checking each
item one at a time and per page.
On Tuesday, October 31, 2017 at 11:47:06 AM
Roberto - not sure if I need to run the migration script to fix my
folder/cabinet problem, but below is what I get as output so not sure what
to do.
thanks.
mayan-worker: started
(mayan-edms) root@sjc1-mayan01:/usr/share/mayan-edms# mayan-edms.py migrate
Operations to perform:
gt; it is now built-in.
>
> On Tuesday, March 14, 2017 at 6:03:27 PM UTC-4, Victor Zele wrote:
>>
>> Beta2 seems to have the same issue with MAYAN_VERSION having the 'b'.
>>
>>
>> File
>> "/usr/share/mayan-edms/local/lib/python2.7/site-packages/cabinets/com
I am trying to switch from folders to cabinets on the 2.2 beta1 release.
When running the migrate command I see the errors below.
regards,
Victor
(mayan-edms) root@sjc1-mayan01:/usr/share/mayan-edms# mayan-edms.py migrate
Traceback (most recent call last):
File
le to add an extra set of parenthesis and a comma like this:
>
>
> https://gitlab.com/mayan-edms/mayan-edms/commit/5abb6784333ee01c1808f51c4165dd0a2ae652b2
>
>
> On Thursday, March 9, 2017 at 1:51:53 AM UTC-4, Victor Zele wrote:
>>
>> nginx log shows:
>>
>&g
pstream:
"uwsgi://unix:/usr/share/mayan-edms/uwsgi.sock:", host:
"sjc1-mayan01.vimo.com"
On Wednesday, March 8, 2017 at 4:01:10 PM UTC-8, Victor Zele wrote:
>
> Hi,
>
> I see the below in my worker/beat error logs when trying to bring up the
> new beta 2
Hi,
I see the below in my worker/beat error logs when trying to bring up the
new beta 2.2 version.
File
"/usr/share/mayan-edms/local/lib/python2.7/site-packages/djcelery/management/base.
py", line 60, in CeleryCommand
options = BaseCommand.option_list
AttributeError: type object
dms/mayan-edms/commit/26f17b6ede3823163558f4c16983bdb6a5bccad6
> )
>
> On Monday, February 6, 2017 at 4:24:38 PM UTC-4, Victor Zele wrote:
>>
>> Just a heads up for anyone updating to 2.1.7, the
>> /usr/share/mayan-edms/mayan/settings/local.py file get reset to a new key
>> so no
Just a heads up for anyone updating to 2.1.7, the
/usr/share/mayan-edms/mayan/settings/local.py file get reset to a new key
so no documents or logins work after the update.
Steps to restore functioning system is to restore the local.py from a
backup and re-run the "mayan-edms.py
We have several watch folders setup for contracts, invoices, quotes, etc.
It would be nice if Mayan would validate a new document does not exist
already in the system by checking maybe an MD5 checksum table of current
documents in the system and reject the new document as already existing.
Issue resolved today. Its a new permission under the roles I needed to
add to our IT folks group. Now they can view the document versions fine.
On Friday, August 26, 2016 at 11:13:20 AM UTC-7, Victor Zele wrote:
>
> I see the below errors in my uwsgi.log file.
>
>
> navigatio
I see the below error now when trying the view any document versions. May
be a regression in the recent releases?
thanks,
Victor
URL shows, http://mayan..com/documents/11196/version/all/
Server error
There's been an error. It's been reported to the site administrators via
e-mail and
This is a new feature that could be possible to implement in the future. I
have an encrypted volume on my server to store documents at rest currently,
so less important than workflow features, etc. being worked on now. We
then rely on access permissions from Mayan that is very good per
I can try that if you think its easier.
On Thursday, June 16, 2016 at 4:10:28 PM UTC-7, Roberto Rosario wrote:
>
> How about switching documentation to something like http://www.mkdocs.org/?
> Uses markdown which simpler.
> On Jun 16, 2016 6:47 PM, "Victor Zele" &l
t; On Tuesday, April 26, 2016 at 5:34:49 PM UTC-5, Roberto Rosario wrote:
>>
>> Thank you for confirming that this still works!
>>
>> On Friday, April 22, 2016 at 1:11:21 PM UTC-4, Victor Zele wrote:
>>>
>>> I can confirm this works for 2.0.2 LDAP authentic
Hi
I am setting up several watch folders for different document types and
would like to set a destination folder for a document type.
Any way to do this now or is this a new feature for watch folders, etc.
thanks!
--
*CONFIDENTIALITY NOTICE: *
*This transmission may contain information
I can confirm this works for 2.0.2 LDAP authentication adding to the
local.py settings file. The usable password is marked red which is correct
since the password is managed in LDAP/AD.
--
*CONFIDENTIALITY NOTICE: *
*This transmission may contain information which is Vimo, Inc. (DBA
As part of our invoice workflow setup in testing mayan-edms, we would like
to use the tags fields that are displayed nicely on the doc list page in
color when a state changes.
Is this possible to add to the workflow state transition an option to add a
tag like "approved" when transitioning to
36 matches
Mail list logo
