[Mayan EDMS: 2653] Re: Filtering a document queryset on the ACL/role name
And it would be neat to have some document info/metadata be made available as extended file attributes through listxattr and getxattr... On Thursday, August 9, 2018 at 2:32:56 PM UTC-4, LeVon Smoker wrote: > > I ended up creating my own version of the mountindex management command in > a custom app > > On Wednesday, August 8, 2018 at 5:16:01 PM UTC-4, Roberto Rosario wrote: >> >> 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 the mountindex feature. >> >> On Tuesday, July 31, 2018 at 8:52:01 AM UTC-4, LeVon Smoker wrote: >>> >>> I figured it out eventually. In the >>> mirroring/management/commands/mountindex.py, I added... >>> acls = AccessControlList.objects.filter(role__label='My Role', >>> permissions__name='document_view') >>> queryset = queryset.filter(acls__in=acls) >>> >>> >>> >>> On Friday, July 27, 2018 at 10:12:21 AM UTC-4, LeVon Smoker wrote: >>>> >>>> How can I do this? I intend to make my own version of the mountindex >>>> command that would allow filtering documents based on a role. I assume >>>> it's >>>> like filtering on a Generic Relation, but I can't figure it out... >>>> >>>> >>>> https://docs.djangoproject.com/en/1.11/ref/contrib/contenttypes/#django.contrib.contenttypes.fields.GenericRelation >>>> >>> -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 2637] Re: Customize the search form
Using a custom app, I overrode (is that a word?) the appearance/home.html
template to point at my own url on the Advanced button ({% url
'my_overrides:search_advanced' search_model='documents.Document' %}). From
there it was creating custom versions of AdvancedSearchForm,
AdvancedSearchView, and ResultsView to get what I wanted. My version of
AdvancedSearchForm adds a ModelMultipleChoiceField which provides an
autocomplete way to find specific documents.
In my AdvancedSearchForm, I was able to change the label on a field - Label
- to Name (users were confused - "where's the document name?")
On Wednesday, August 8, 2018 at 5:11:44 PM UTC-4, Roberto Rosario wrote:
>
> 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 Tuesday, July 31, 2018 at 2:17:45 PM UTC-4, LeVon Smoker wrote:
>>
>> Is there a good way to do this to...
>> - change the field labels
>> - add a custom search widget (autocomplete)
>>
>> As always, I don't want to hack the original source code...
>>
>> Thanks.
>>
>
--
---
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 2636] Re: Filtering a document queryset on the ACL/role name
I ended up creating my own version of the mountindex management command in a custom app On Wednesday, August 8, 2018 at 5:16:01 PM UTC-4, Roberto Rosario wrote: > > 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 the > mountindex feature. > > On Tuesday, July 31, 2018 at 8:52:01 AM UTC-4, LeVon Smoker wrote: >> >> I figured it out eventually. In the >> mirroring/management/commands/mountindex.py, I added... >> acls = AccessControlList.objects.filter(role__label='My Role', >> permissions__name='document_view') >> queryset = queryset.filter(acls__in=acls) >> >> >> >> On Friday, July 27, 2018 at 10:12:21 AM UTC-4, LeVon Smoker wrote: >>> >>> How can I do this? I intend to make my own version of the mountindex >>> command that would allow filtering documents based on a role. I assume it's >>> like filtering on a Generic Relation, but I can't figure it out... >>> >>> >>> https://docs.djangoproject.com/en/1.11/ref/contrib/contenttypes/#django.contrib.contenttypes.fields.GenericRelation >>> >> -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 2394] Search in Document preview
Has anyone come up with a customization that allows searching a single document while previewing it? What our users do now is download and then use Word or Adobe Reader search functionality. I sometimes go to Content, then do Ctrl-F in the browser, but I think a more native "quick document search" would be nice - especially for our phone number directories. -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 2326] Re: Printing oddity
I am running the latest 2.7.3 development branch. On Thursday, March 8, 2018 at 8:52:18 AM UTC-5, LeVon Smoker wrote: > > When printing a document from the Actions menu, I am getting four lines > which all say "text" on them at the end of every document. The browser > print window doesn't show this, but the OS-level print preview does as well > as the paper printout. It happens in any browser. > > I have attached a PDF of the print preview and the actual docx document. > -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 2317] Re: Help with Permissions
Michael,
Is it possible to get read access to
https://gitlab.com/Michael.Price/mayan-edms/commits/feature/pagesearch_testing?
On Friday, March 2, 2018 at 10:13:05 AM UTC-5, LeVon Smoker wrote:
>
> Thanks!!
>
> On Thursday, March 1, 2018 at 10:56:31 PM UTC-5, Michael Price wrote:
>>
>> The fix for the cabinet pagination was easy. Just make CabinetDetailView
>> a subclass of DocumentListView instead of TemplateView. In the
>> cabinet_details.html remove the lines {% with document_list as object_list
>> %} and {% endwith %} This makes the template display the paginated
>> object_list provided by DocumentListView and not the raw list of documents
>> in the document_list variable.
>>
>> On Thursday, March 1, 2018 at 7:06:03 PM UTC-4, Michael Price wrote:
>>>
>>> Found the root of the problem. DocumentPage is registered with the
>>> permission inheritance but the model returned during page searches is not
>>> DocumentPage but DocumentPageResult. DocumentPageResult has not permission
>>> inheritance relationship to Document. That is the reason no pages are
>>> returned unless you are an admin user.
>>>
>>> The fix involves a few steps:
>>>
>>> 1- Add a permission relationship between DocumentPageResult and
>>> Document. This causes an error. The error is caused because the inheritance
>>> system only allows database fields or functions, doesn't support related
>>> references. In this case a related references is needed: DocumentPageResult
>>> -> DocumentVersion -> Document. The related field must allow something like
>>> 'document_version__document".
>>> 2- Add a function to navigate a related reference down to the actual
>>> model instance being referenced. This function turns the string
>>> 'document_version__document" to the instance of Document being referenced.
>>> 3- Update the AccessControlList.objects.filter_by_access method to use
>>> the return_related instead of the simple getattr.
>>>
>>> This solution allows filtering the queryset at the database instead of
>>> using callable function for each instance in the queryset which is much
>>> faster and cleaner.
>>>
>>> My code in the branch 'feature/pagesearch_testing' at
>>> https://gitlab.com/Michael.Price/mayan-edms/commits/feature/pagesearch_testing.
>>>
>>> Added a 4 tests for document and document page searching with and without
>>> the document view permissions and they pass with no problem. I think every
>>> app that has a searchable object should have a test_search test suit.
>>>
>>> Even after months of working on the code I'm still amazed at how well
>>> written Mayan is. Kudos to Roberto for making something so far ahead than
>>> anything else I've seen in the Django market.
>>>
>>> I'll take a stab at the Cabinet pagination problem.
>>>
>>> Just helping until Roberto is back in full swing :)
>>>
>>> On Thursday, March 1, 2018 at 3:13:27 PM UTC-4, lonevi...@gmail.com
>>> wrote:
>>>>
>>>> I was referring to Mayan's custom permission inheritance which is
>>>> handled by the acls.classes.ModelPermission class. This is different than
>>>> the model inheritance used by Django which is limited to just database
>>>> fields and methods. Django's model inheritance is meant to emulate
>>>> Python's
>>>> class inheritance whose purpose is reduce repetition of code. Mayan
>>>> permission inheritance should be called permission relationships instead
>>>> to
>>>> better reflect its purpose.
>>>>
>>>> Mayan uses two method of the ModelPermission to determine how an object
>>>> inherit permission from another. In the documents.apps file it is using
>>>> the
>>>> .register_inheritance to correlate the DocumentPage and the Document model.
>>>>
>>>> ModelPermission.register_inheritance(
>>>> model=DocumentPage, related='document',
>>>> )
>>>>
>>>> Before that it is using the .register_proxy to correlate the Document
>>>> model with the DocumentType model. I don't understand the difference. I'm
>>>> tying to figure it out before bothering Roberto for an explanation.
>>>>
>>>> On Thursday, March 1, 2018 at 10:14:50 AM UTC-4, LeVon Smoker wrote:
>>>>>
>>>>> Yes. This specific case is with the DocumentPageResu
[Mayan EDMS: 2260] Re: Pagination patch for Cabinets Details
Answering my own question...
Patch mayan/apps/cabinets/views.py b/mayan/apps/cabinets/views.py:
Add at/near the top:
from django.views.generic.list import MultipleObjectMixin
from django.conf import settings
from pure_pagination import Paginator, EmptyPage, PageNotAnInteger
from pure_pagination.mixins import PaginationMixin
Modify the CabinetDetailView class adding PaginationMixin,
MultipleObjectMixin and paginate_by:
class CabinetDetailView(PaginationMixin, MultipleObjectMixin, TemplateView):
template_name = 'cabinets/cabinet_details.html'
+paginate_by = settings.COMMON_PAGINATE_BY
Replace the get_context_data function:
def get_context_data(self, **kwargs):
self.object_list = self.get_document_queryset()
try:
page = self.request.GET.get('page', 1)
except PageNotAnInteger:
page = 1
p = Paginator(self.object_list, self.paginate_by, request=self.
request)
document_list = p.page(page).object_list
data = super(CabinetDetailView, self).get_context_data(**kwargs)
cabinet = self.get_object()
data.update(
{
'jstree_data': '\n'.join(
jstree_data(node=cabinet.get_root(), selected_node=
cabinet)
),
'document_list': document_list,
'hide_links': True,
'list_as_items': True,
'object': cabinet,
'title': _('Details of cabinet: %s') % cabinet.get_full_path
(),
}
)
return data
Standard disclaimers: not rigorously tested, it works for me, your mileage
may vary
On Wednesday, January 24, 2018 at 8:31:46 AM UTC-5, LeVon Smoker wrote:
>
> Has anyone developed a patch to add pagination for the documents view when
> going in through the Cabinets menu / All / Details? We have a cabinet with
> over 1000 documents in it, and the page takes minutes (or the browser locks
> up) to render all of them documents/thumbnails.
>
--
---
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 2249] Pagination patch for Cabinets Details
Has anyone developed a patch to add pagination for the documents view when going in through the Cabinets menu / All / Details? We have a cabinet with over 1000 documents in it, and the page takes minutes (or the browser locks up) to render all of them documents/thumbnails. -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 2013] Upload wizard question
Roberto, Is there a release target date for the document upload wizard refactor? Specifically, I'm looking for the ability to add cabinets during upload. In the mean time, what's the best way to hack in cabinets on the upload wizard? Thanks, LeVon Smoker -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1991] Re: Adding Dashboard Widget
This is awesome. Thanks for the quick responses.
On Wednesday, August 9, 2017 at 1:39:36 PM UTC-4, LeVon Smoker wrote:
>
> I have a custom app (hrcsb_overrides) where I have am keeping my
> customizations to Mayan. I added the below code to try to add a widget to
> the home page as a shortcut to Cabinets (also to experiment).
> Cabinet = self.get_model('Cabinet')
>
> DashboardWidget(
> icon='fa fa-folder',
> queryset=Cabinet.objects.all(),
> label=_('Cabinets'),
> link=reverse_lazy('cabinets:cabinet_list')
> )
>
> The call to get_model generates an error
> LookupError: App 'hrcsb_overrides' doesn't have a 'Cabinet' model.
>
>
> which I understand but I can't figure my way around this. Maybe I'm in the
> wrong place...
>
> Thanks,
> LeVon Smoker
>
--
---
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1982] Re: Removing menus
Actually I didn't figure this out...
On Tuesday, August 8, 2017 at 11:26:51 AM UTC-4, LeVon Smoker wrote:
>
> Is the procedure for removing menus from the home page the same as it used
> to be? I had been removing the Tags menu, but at some point the code
> stopped working. The formerly-working code is:
>
> from __future__ import unicode_literals
>
> from django.utils.translation import ugettext_lazy as _
>
> from common import MayanAppConfig
>
> from common import menu_main
> from folders.links import link_folder_list
> from tags.links import link_tag_list
>
> class HRCSBOverridesApp(MayanAppConfig):
> name = 'hrcsb_overrides'
> verbose_name = _('HRCSB Overrides')
>
> def ready(self):
> super(HRCSBOverridesApp, self).ready()
>
> # Remove "Tags" links from main menu
> menu_main.unbind_links(
> links=(link_tag_list,),
> )
> mayan/apps/hrcsb_overrides/apps.py
>
> Thanks,
> LeVon Smoker
>
--
---
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1981] Error while testing a Mailing profile
I get an error while testing a Django SMTP backend mailing profile. This is
on the 2.6.4 pypi release.
Traceback:
File
"/usr/share/mayan-edms/local/lib/python2.7/site-packages/django/core/handlers/exception.py"
in inner
42. response = get_response(request)
File
"/usr/share/mayan-edms/local/lib/python2.7/site-packages/django/core/handlers/base.py"
in _legacy_get_response
249. response = self._get_response(request)
File
"/usr/share/mayan-edms/local/lib/python2.7/site-packages/django/core/handlers/base.py"
in _get_response
187. response = self.process_exception_by_middleware(e,
request)
File
"/usr/share/mayan-edms/local/lib/python2.7/site-packages/django/core/handlers/base.py"
in _get_response
185. response = wrapped_callback(request, *callback_args,
**callback_kwargs)
File
"/usr/share/mayan-edms/local/lib/python2.7/site-packages/django/views/generic/base.py"
in view
68. return self.dispatch(request, *args, **kwargs)
File "/usr/share/mayan-edms/mayan/apps/common/mixins.py" in dispatch
350. ).dispatch(request, *args, **kwargs)
File "/usr/share/mayan-edms/mayan/apps/common/mixins.py" in dispatch
315. ).dispatch(request, *args, **kwargs)
File
"/usr/share/mayan-edms/local/lib/python2.7/site-packages/django/views/generic/base.py"
in dispatch
88. return handler(request, *args, **kwargs)
File
"/usr/share/mayan-edms/local/lib/python2.7/site-packages/django/views/generic/edit.py"
in post
183. return self.form_valid(form)
File "/usr/share/mayan-edms/mayan/apps/mailer/views.py" in form_valid
239. self.get_user_mailer().test(to=(form.cleaned_data['email'],))
File "/usr/share/mayan-edms/mayan/apps/mailer/models.py" in test
109. self.send(to=to, subject=_('Test email from Mayan EDMS'))
File "/usr/share/mayan-edms/mayan/apps/mailer/models.py" in send
86. recipient_list = split_recipient_list(recipients=[to])
File "/usr/share/mayan-edms/mayan/apps/mailer/utils.py" in
split_recipient_list
16. result.extend(recipient.split(separator))
Exception Type: AttributeError at /mailer/user_mailers/1/test/
Exception Value: 'tuple' object has no attribute 'split'
Oddly enough, sending mail works fine when emailing a document link.
Thanks,
LeVon Smoker
--
---
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1980] Re: Removing menus
Figured it out.
On Tuesday, August 8, 2017 at 11:26:51 AM UTC-4, LeVon Smoker wrote:
>
> Is the procedure for removing menus from the home page the same as it used
> to be? I had been removing the Tags menu, but at some point the code
> stopped working. The formerly-working code is:
>
> from __future__ import unicode_literals
>
> from django.utils.translation import ugettext_lazy as _
>
> from common import MayanAppConfig
>
> from common import menu_main
> from folders.links import link_folder_list
> from tags.links import link_tag_list
>
> class HRCSBOverridesApp(MayanAppConfig):
> name = 'hrcsb_overrides'
> verbose_name = _('HRCSB Overrides')
>
> def ready(self):
> super(HRCSBOverridesApp, self).ready()
>
> # Remove "Tags" links from main menu
> menu_main.unbind_links(
> links=(link_tag_list,),
> )
> mayan/apps/hrcsb_overrides/apps.py
>
> Thanks,
> LeVon Smoker
>
--
---
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 mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1364] Re: Debugging
Ah, thanks. I was expecting to see something different on error pages. Now I recall seeing something in the docs. On Tuesday, May 17, 2016 at 4:02:32 PM UTC-4, Roberto Rosario wrote: > > Setting DEBUG to True will allow you to use the command ``runserver`` with > full debug output. Examples attached. > > We fixed the issue with the sources editing and are doing final testing > before releasing bugfix version 2.1.1 > > On Tuesday, May 17, 2016 at 3:23:05 PM UTC-4, LeVon Smoker wrote: >> >> I found that the upgrade only partially migrated the database changes. >> After running 'mayan-edms.py performupgrade' a second time all my 'Server >> errors' went away except for when I try to edit Sources. >> >> Note: using MySQL 5.5.47 >> >> On Tuesday, May 17, 2016 at 11:15:21 AM UTC-4, LeVon Smoker wrote: >>> >>> What is supposed to happen when the DEBUG setting in local.py is set to >>> True? I can't see any difference in any of the log files. Are all of the >>> messages sent to the console? >>> >>> My root problem is that after upgrading from 2.0.2 to 2.1, I get a >>> "Server error" when trying to delete trashed documents, go into the new >>> MOTD, and edit sources. >>> >>> Thanks, >>> LeVon S. >>> >> -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1361] Debugging
What is supposed to happen when the DEBUG setting in local.py is set to True? I can't see any difference in any of the log files. Are all of the messages sent to the console? My root problem is that after upgrading from 2.0.2 to 2.1, I get a "Server error" when trying to delete trashed documents, go into the new MOTD, and edit sources. Thanks, LeVon S. -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1286] Re: Watch Folder Network Address
Much depends on how your system/installation is configured. You need to ensure that the user that Mayan is running under (which might be in your uwsgi.ini file) has access to the mount directory. Then use chown and/or chmod on that directory. Beyond that info, look for general help on unix/linux permissions. On Friday, February 19, 2016 at 4:14:21 AM UTC-5, Stefan Hagel wrote: > > Thank you Levon! > That got me a lot further. > > Do you know how the change the permissions for the Folder and Files so > Mayan can read and write them? > Right now i get an "Error processing source: [Errno 13] Permission denied" > > -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1281] Re: Watch Folder Network Address
I mounted the network share to a local directory by adding a line in my /etc/fstab file. //mysmbserver/Mayan_EDMS_Document_Storage/ /media/staging_folder cifs credentials=/etc/smbcredentials,iocharset=utf8 0 0 The file /etc/smbcreddentials has this: username=myusername password=mysecretpassword domain=mydomain LeVon S. On Wednesday, February 17, 2016 at 10:37:34 AM UTC-5, Stefan Hagel wrote: > > Hello, > > is it possible to use a Networkfolder as a watchfolder? > > I've tried nummerous combinations but nothing works. > Last try was: smb://192.168.178.132/Hagel_Daten/MayanEDMS > > Greetings, > Stefan > -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1280] Date added on documents
Why does the 'Date added' field show in UTC when viewing a document's properties, but show in local time when viewing the document rows through the admin interface? I'd like both to show in my local time which I have set in mayan/settings/local.py with TIME_ZONE = 'America/New_York' Thanks. LeVon S. -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1274] Re: A cosmetic bug and a question
Deleting and re-creating the Index fixed the problem. On Tuesday, February 16, 2016 at 1:05:08 AM UTC-5, Roberto Rosario wrote: > > Thanks for these, I fixed the HTML tags issue and it is part of version > 2.0.2 ( > https://gitlab.com/mayan-edms/mayan-edms/commit/3fdc5e523ad58d531f574c63731fb73e4c805823). > > > > I was unable to to recreate the unnamed index node behavior you showed. > Can you provide a step of steps (including order) that consistently > recreates the issue? If it can be in as little steps as possible so I can > write a test, the better. If not, not a problem and I can recreate the > issue by hand and debug. > > Thanks LeVon. > > On Thursday, February 11, 2016 at 3:39:06 PM UTC-4, LeVon Smoker wrote: >> >> In the first attached screenshot... >> >> 1. the title of the page when viewing Indexes contains HTML - no big deal >> just not pretty >> 2. what would cause a blank entry in the Node list? (The second attached >> screenshot shows the Index definition.) There are 4 documents of the type >> 'Agency Documents' >> >> Thanks. >> >> LeVon S. >> >> >> >> -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1273] Re: A cosmetic bug and a question
Excellent! On the index issue, unfortunately my boss uploaded the docs and created the indexes so I have no idea how the empty one got there. Any pointers on how I might debug? LeVon S. On Tuesday, February 16, 2016 at 1:05:08 AM UTC-5, Roberto Rosario wrote: > > Thanks for these, I fixed the HTML tags issue and it is part of version > 2.0.2 ( > https://gitlab.com/mayan-edms/mayan-edms/commit/3fdc5e523ad58d531f574c63731fb73e4c805823). > > > > I was unable to to recreate the unnamed index node behavior you showed. > Can you provide a step of steps (including order) that consistently > recreates the issue? If it can be in as little steps as possible so I can > write a test, the better. If not, not a problem and I can recreate the > issue by hand and debug. > > Thanks LeVon. > > On Thursday, February 11, 2016 at 3:39:06 PM UTC-4, LeVon Smoker wrote: >> >> In the first attached screenshot... >> >> 1. the title of the page when viewing Indexes contains HTML - no big deal >> just not pretty >> 2. what would cause a blank entry in the Node list? (The second attached >> screenshot shows the Index definition.) There are 4 documents of the type >> 'Agency Documents' >> >> Thanks. >> >> LeVon S. >> >> >> >> -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1252] A cosmetic bug and a question
In the first attached screenshot... 1. the title of the page when viewing Indexes contains HTML - no big deal just not pretty 2. what would cause a blank entry in the Node list? (The second attached screenshot shows the Index definition.) There are 4 documents of the type 'Agency Documents' Thanks. LeVon S. -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1242] Update checkbox
What is the intended effect of the 'Update' checkbox on the Upload Document form? -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1243] Update checkbox
What is the intended effect of the 'Update' checkbox on the Upload Document form? -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1216] Re: Suggestions for handling security
Thanks very much. That's the direction I was going. On Tuesday, January 12, 2016 at 3:20:04 AM UTC-5, Roberto Rosario wrote: > > Hi, thanks for trying out Mayan EDMS. > > Because any given document can be of only 1 document type, you would need > to add the department name as part of the document type label. > Also because these permissions are for specific document types, grant the > permission to the role in the *document type ACL* not in the role > creation view (as there the permissions are global). > > Document type Role > > -- > Global document all roles -> document view, editors role -> upload, > checkin > Department_1_docs dept_1_view -> document view, dept_1_editors -> > upload, checkin > Department_2_docs dept_1_view -> document view, dept_1_editors -> > upload, checkin > > Example: > Document types > -- > "Accounting - Invoices" > "Human resources - complaint" > > Roles > > "Accounting read only" > "Accounting editors" > "Human resources read only" > "Human resources editors" > > Document type ACLs (document type vs. role + permissions) > -- > "Accounting - Invoices" -> "Accounting read only" -> [document view] > "Accounting - Invoices" -> "Accounting editor" -> [extra permissions] > "Human resources - complaint" -> "Human resources read only" -> [document > view] > "Human resources - complaint" -> "Human resources editors" -> [extra > permissions] > > Hope this setup works for you. > > On Thursday, January 7, 2016 at 1:32:34 PM UTC-4, LeVon Smoker wrote: >> >> We are deploying Mayan-EDMS. It seems to be very well-designed and >> flexible. Thanks Roberto (and others) for this excellent app! >> >> I am having trouble, though, in figuring out how to optimally set up >> roles/ACLs/groups/doctypes for the security setup that the management would >> like. >> >> I have our Active Directory groups mirrored so we can have some control >> within the AD management software. On a "permissions" level we envision >> Readers (view-only) and Editors (view/upload/checkin/out). We would like >> agency-wide documents to be viewable by all staff (Readers) and manageable >> (Editors) by a management group. We would also like for department-specific >> documents to be limited to that department (for viewing, ie, Readers) and >> then within that department have a team that can manage the documents >> (Editors). >> >> Is this way of doing security possible or do we need to simplify what we >> want? >> >> LeVon Smoker >> > -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1218] Django ORM
I've had a few failed attempts at getting to the data through the Django ORM. I'd like to get at the ACLs model so I can create a bunch of document types (via a script) with varying roles and identical permissions lists. Is the ORM a reasonable way to do this? -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1207] Document renaming app
I added this app to my installation, but then I realized that all documents I uploaded had names like 'Document stub, id: 9' instead of the uploaded file name (even with no renaming templates defined). Disabling the app in settings/local.py fixed the problem. Is this a bug or is there something that I need to configure after installing the document_renaming app? -- --- 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 mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
