[Mayan EDMS: 123] Mayan EDMS v0.12 released!

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Mayan EDMS: 123] Mayan EDMS v0.12 released!

rosarior
Administrator
Thanks to everybody that have helped with Mayan EDMS, it hasn't been easy, but it would have been much harder if it wasn't for your help, thanks!

Download/fork, hack, enjoy!


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Mayan EDMS: 123] Re: Mayan EDMS v0.12 released!

Сергей Глита
Thank you, Roberto, congratulations to the new achievements.

On 1 мар, 23:20, Roberto Rosario <[hidden email]>
wrote:
> Thanks to everybody that have helped with Mayan EDMS, it hasn't been easy,
> but it would have been much harder if it wasn't for your help, thanks!
>
> Download/fork, hack, enjoy!
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Mayan EDMS: 134] Re: Mayan EDMS v0.12 released!

rosarior
Administrator
On 03/02/2012 12:47 AM, Сергей Глита wrote:
> Thank you, Roberto, congratulations to the new achievements.
>
> On 1 мар, 23:20, Roberto Rosario <[hidden email]>
> wrote:
>> Thanks to everybody that have helped with Mayan EDMS, it hasn't been easy,
>> but it would have been much harder if it wasn't for your help, thanks!
>>
>> Download/fork, hack, enjoy!
>
Thanks Sergei!

--
Roberto Rosario
GPG key: D210724D


signature.asc (566 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Mayan EDMS: 138] Re: Mayan EDMS v0.12 released!

Сергей Глита
In reply to this post by rosarior
Hi, Roberto!
Search does not work for the field "comment"
Maybe it's because pgsql
Django sends the following query

'SELECT "documents_document"."id" FROM "documents_document" LEFT OUTER
JOIN "documents_documenttype" ON
("documents_document"."document_type_id" =
"documents_documenttype"."id") LEFT OUTER JOIN
"documents_documentversion" ON ("documents_document"."id" =
"documents_documentversion"."document_id") LEFT OUTER JOIN
"metadata_documentmetadata" ON ("documents_document"."id" =
"metadata_documentmetadata"."document_id") LEFT OUTER JOIN
"documents_documentpage" ON ("documents_documentversion"."id" =
"documents_documentpage"."document_version_id") LEFT OUTER JOIN
"taggit_taggeditem" ON ("documents_document"."id" =
"taggit_taggeditem"."object_id") LEFT OUTER JOIN "taggit_tag" ON
("taggit_taggeditem"."tag_id" = "taggit_tag"."id") LEFT OUTER JOIN
"django_comments" ON ("documents_document"."id" =
"django_comments"."object_pk") WHERE
(UPPER("documents_documenttype"."name"::text) LIKE UPPER(%s)  OR
UPPER("documents_documentversion"."mimetype"::text) LIKE UPPER(%s)  OR
UPPER("documents_documentversion"."filename"::text) LIKE UPPER(%s)  OR
UPPER("metadata_documentmetadata"."value"::text) LIKE UPPER(%s)  OR
UPPER("documents_documentpage"."content"::text) LIKE UPPER(%s)  OR
UPPER("documents_document"."description"::text) LIKE UPPER(%s)  OR
(UPPER("taggit_tag"."name"::text) LIKE UPPER(%s)  AND
"taggit_taggeditem"."content_type_id" = %s ) OR
(UPPER("django_comments"."comment"::text) LIKE UPPER(%s)  AND
"django_comments"."content_type_id" = %s )) ORDER BY
"documents_document"."date_added" DESC'

and scolds me for

ERROR:  operator does not exist: integer = text
LEFT OUTER JOIN "django_comments" ON ("documents_document"."id" =
"django_comments"."object_pk")
No operator matches the given name and argument type(s). You might
need to add explicit type casts.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Mayan EDMS: 139] Re: Mayan EDMS v0.12 released!

rosarior
Administrator

Yes, Postgresql complains about some parts of the search code whereas MySQL and SQLite work Ok.  This one of the reasons I'm switching Mayan to a dedicated engine like Haystack, it is planned to be done during this development cycle right when I finish the inital workflow app.

On Mar 16, 2012 2:40 AM, "Сергей Глита" <[hidden email]> wrote:
Hi, Roberto!
Search does not work for the field "comment"
Maybe it's because pgsql
Django sends the following query

'SELECT "documents_document"."id" FROM "documents_document" LEFT OUTER
JOIN "documents_documenttype" ON
("documents_document"."document_type_id" =
"documents_documenttype"."id") LEFT OUTER JOIN
"documents_documentversion" ON ("documents_document"."id" =
"documents_documentversion"."document_id") LEFT OUTER JOIN
"metadata_documentmetadata" ON ("documents_document"."id" =
"metadata_documentmetadata"."document_id") LEFT OUTER JOIN
"documents_documentpage" ON ("documents_documentversion"."id" =
"documents_documentpage"."document_version_id") LEFT OUTER JOIN
"taggit_taggeditem" ON ("documents_document"."id" =
"taggit_taggeditem"."object_id") LEFT OUTER JOIN "taggit_tag" ON
("taggit_taggeditem"."tag_id" = "taggit_tag"."id") LEFT OUTER JOIN
"django_comments" ON ("documents_document"."id" =
"django_comments"."object_pk") WHERE
(UPPER("documents_documenttype"."name"::text) LIKE UPPER(%s)  OR
UPPER("documents_documentversion"."mimetype"::text) LIKE UPPER(%s)  OR
UPPER("documents_documentversion"."filename"::text) LIKE UPPER(%s)  OR
UPPER("metadata_documentmetadata"."value"::text) LIKE UPPER(%s)  OR
UPPER("documents_documentpage"."content"::text) LIKE UPPER(%s)  OR
UPPER("documents_document"."description"::text) LIKE UPPER(%s)  OR
(UPPER("taggit_tag"."name"::text) LIKE UPPER(%s)  AND
"taggit_taggeditem"."content_type_id" = %s ) OR
(UPPER("django_comments"."comment"::text) LIKE UPPER(%s)  AND
"django_comments"."content_type_id" = %s )) ORDER BY
"documents_document"."date_added" DESC'

and scolds me for

ERROR:  operator does not exist: integer = text
LEFT OUTER JOIN "django_comments" ON ("documents_document"."id" =
"django_comments"."object_pk")
No operator matches the given name and argument type(s). You might
need to add explicit type casts.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Mayan EDMS: 141] Re: Mayan EDMS v0.12 released!

Alexandru Kiss
Hi, everybody I would like to contribute with a proper italian
translation and system testing (already found some bugs) to Rosarior, do
we already have a bug tracking system or should I prepare one?

Thanks in advance
Alexandru Kiss
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Mayan EDMS: 142] Re: Mayan EDMS v0.12 released!

Pierpaolo Baldan

Ciao Alexandrus
feel you free to make a better italian translation, have you found some translation's parts that are not so good ?
Could you tell me where I made mistakes ?
Pierpaolo
 
Il giorno 20 marzo 2012 09:38, Alexandru Kiss <[hidden email]> ha scritto:
Hi, everybody I would like to contribute with a proper italian translation and system testing (already found some bugs) to Rosarior, do we already have a bug tracking system or should I prepare one?

Thanks in advance
Alexandru Kiss

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Mayan EDMS: 143] Re: Mayan EDMS v0.12 released!

Alexandru Kiss
Il 20/03/2012 09:48, Pierpaolo Baldan ha scritto:

Ciao Alexandrus
feel you free to make a better italian translation, have you found some translation's parts that are not so good ?
Could you tell me where I made mistakes ?
Pierpaolo
 
Il giorno 20 marzo 2012 09:38, Alexandru Kiss <[hidden email]> ha scritto:
Hi, everybody I would like to contribute with a proper italian translation and system testing (already found some bugs) to Rosarior, do we already have a bug tracking system or should I prepare one?

Thanks in advance
Alexandru Kiss

well in the menu A rigurdo should be A riguardo , then there are some things not translated at all aka in the Configura there is an english part (by the way I would call that Configurazione) , it's not my itent to upset anyone I am just a mere tester of the app and would like to help with it.

Alex
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Mayan EDMS: 144] Re: Mayan EDMS v0.12 released!

Pierpaolo Baldan
ASAP I will make the changes.

Thanks, Pierpaolo
Il giorno 20 marzo 2012 09:51, Alexandru Kiss <[hidden email]> ha scritto:
Il 20/03/2012 09:48, Pierpaolo Baldan ha scritto:

Ciao Alexandrus
feel you free to make a better italian translation, have you found some translation's parts that are not so good ?
Could you tell me where I made mistakes ?
Pierpaolo
 
Il giorno 20 marzo 2012 09:38, Alexandru Kiss <[hidden email]> ha scritto:
Hi, everybody I would like to contribute with a proper italian translation and system testing (already found some bugs) to Rosarior, do we already have a bug tracking system or should I prepare one?

Thanks in advance
Alexandru Kiss

well in the menu A rigurdo should be A riguardo , then there are some things not translated at all aka in the Configura there is an english part (by the way I would call that Configurazione) , it's not my itent to upset anyone I am just a mere tester of the app and would like to help with it.

Alex

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Mayan EDMS: 146] Re: Mayan EDMS v0.12 released!

rosarior
Administrator
In reply to this post by Alexandru Kiss
Translation management is done using Transifex, just create an account and go to https://www.transifex.net/projects/p/mayan-edms/  to start translating strings, the Italian translation is at %90 so there is some work to be done, more so when I upload the new messages from the new email and workflow apps.  For the issue tracker use the: https://github.com/rosarior/mayan/issues 


Thanks

On Tuesday, March 20, 2012 4:51:05 AM UTC-4, TANATHOS wrote:
Il 20/03/2012 09:48, Pierpaolo Baldan ha scritto:

Ciao Alexandrus
feel you free to make a better italian translation, have you found some translation's parts that are not so good ?
Could you tell me where I made mistakes ?
Pierpaolo
 
Il giorno 20 marzo 2012 09:38, Alexandru Kiss <[hidden email]> ha scritto:
Hi, everybody I would like to contribute with a proper italian translation and system testing (already found some bugs) to Rosarior, do we already have a bug tracking system or should I prepare one?

Thanks in advance
Alexandru Kiss

well in the menu A rigurdo should be A riguardo , then there are some things not translated at all aka in the Configura there is an english part (by the way I would call that Configurazione) , it's not my itent to upset anyone I am just a mere tester of the app and would like to help with it.

Alex
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Mayan EDMS: 146] Re: Mayan EDMS v0.12 released!

Pierpaolo Baldan

Ciao Roberto
I just finished the remaining translation ;-))
I'm at your disposal to other parts
Pierpaolo
Il giorno 20 marzo 2012 13:38, Roberto Rosario <[hidden email]> ha scritto:
Translation management is done using Transifex, just create an account and go to https://www.transifex.net/projects/p/mayan-edms/  to start translating strings, the Italian translation is at %90 so there is some work to be done, more so when I upload the new messages from the new email and workflow apps.  For the issue tracker use the: https://github.com/rosarior/mayan/issues 


Thanks


On Tuesday, March 20, 2012 4:51:05 AM UTC-4, TANATHOS wrote:
Il 20/03/2012 09:48, Pierpaolo Baldan ha scritto:

Ciao Alexandrus
feel you free to make a better italian translation, have you found some translation's parts that are not so good ?
Could you tell me where I made mistakes ?
Pierpaolo
 
Il giorno 20 marzo 2012 09:38, Alexandru Kiss <[hidden email]> ha scritto:
Hi, everybody I would like to contribute with a proper italian translation and system testing (already found some bugs) to Rosarior, do we already have a bug tracking system or should I prepare one?

Thanks in advance
Alexandru Kiss

well in the menu A rigurdo should be A riguardo , then there are some things not translated at all aka in the Configura there is an english part (by the way I would call that Configurazione) , it's not my itent to upset anyone I am just a mere tester of the app and would like to help with it.

Alex

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Mayan EDMS: 216] Re: Mayan EDMS v0.12 released!

VítorFigueiró
In reply to this post by rosarior
Roberto Rosario Gonzalez <roberto.rosario.gonzalez@...> writes:

>
>
> Yes, Postgresql complains about some parts of the search code whereas MySQL
and SQLite work Ok.  This one of the reasons I'm switching Mayan to a dedicated
engine like Haystack, it is planned to be done during this development cycle
right when I finish the inital workflow app.
>
> On Mar 16, 2012 2:40 AM, "Сергей Глита"
<[hidden email]> wrote:

> Hi, Roberto!
> Search does not work for the field "comment"
> Maybe it's because pgsql
> Django sends the following query
> 'SELECT "documents_document"."id" FROM "documents_document" LEFT OUTER
> JOIN "documents_documenttype" ON
> ("documents_document"."document_type_id" =
> "documents_documenttype"."id") LEFT OUTER JOIN
> "documents_documentversion" ON ("documents_document"."id" =
> "documents_documentversion"."document_id") LEFT OUTER JOIN
> "metadata_documentmetadata" ON ("documents_document"."id" =
> "metadata_documentmetadata"."document_id") LEFT OUTER JOIN
> "documents_documentpage" ON ("documents_documentversion"."id" =
> "documents_documentpage"."document_version_id") LEFT OUTER JOIN
> "taggit_taggeditem" ON ("documents_document"."id" =
> "taggit_taggeditem"."object_id") LEFT OUTER JOIN "taggit_tag" ON
> ("taggit_taggeditem"."tag_id" = "taggit_tag"."id") LEFT OUTER JOIN
> "django_comments" ON ("documents_document"."id" =
> "django_comments"."object_pk") WHERE
> (UPPER("documents_documenttype"."name"::text) LIKE UPPER(%s)  OR
> UPPER("documents_documentversion"."mimetype"::text) LIKE UPPER(%s)  OR
> UPPER("documents_documentversion"."filename"::text) LIKE UPPER(%s)  OR
> UPPER("metadata_documentmetadata"."value"::text) LIKE UPPER(%s)  OR
> UPPER("documents_documentpage"."content"::text) LIKE UPPER(%s)  OR
> UPPER("documents_document"."description"::text) LIKE UPPER(%s)  OR
> (UPPER("taggit_tag"."name"::text) LIKE UPPER(%s)  AND
> "taggit_taggeditem"."content_type_id" = %s ) OR
> (UPPER("django_comments"."comment"::text) LIKE UPPER(%s)  AND
> "django_comments"."content_type_id" = %s )) ORDER BY
> "documents_document"."date_added" DESC'
> and scolds me for
> ERROR:  operator does not exist: integer = text
> LEFT OUTER JOIN "django_comments" ON ("documents_document"."id" =
> "django_comments"."object_pk")
> No operator matches the given name and argument type(s). You might
> need to add explicit type casts.
>
>

Hi!

just had the same problem... it seems the only issue regarding search with
postgresql is that the comments contrib app uses object_pk instead of object_id
for the GenericForeignKey.

If someone really wants to use postgresql before a permanent fix or new search
engine is available, it works if you paste the following hack at the end of
apps/dynamic_search/models.py:

from django.db import connection
if connection.vendor == 'postgresql':
    from django.db.models.sql.compiler import SQLCompiler
    orig_get_from_clause = SQLCompiler.get_from_clause
    def get_from_clause(self):
        result, extra = orig_get_from_clause(self)
        result = map(lambda s: s.replace('"django_comments"."object_pk"',
                        '"django_comments"."object_pk"::integer'), result)
        return result, extra
    SQLCompiler.get_from_clause = get_from_clause


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Mayan EDMS: 218] Re: Mayan EDMS v0.12 released!

rosarior
Administrator
Wow!  Awesome!  I will include this in the next maintenance release for the 0.12 series.  Thanks a lot!

On Wednesday, July 4, 2012 5:47:22 PM UTC-4, vfigueiro wrote:
Roberto Rosario Gonzalez <roberto.rosario.gonzalez@...> writes:

>
>
> Yes, Postgresql complains about some parts of the search code whereas MySQL
and SQLite work Ok.  This one of the reasons I'm switching Mayan to a dedicated
engine like Haystack, it is planned to be done during this development cycle
right when I finish the inital workflow app.
>
> On Mar 16, 2012 2:40 AM, "Сергей Глита"
<s.v.glita@...com> wrote:

> Hi, Roberto!
> Search does not work for the field "comment"
> Maybe it's because pgsql
> Django sends the following query
> 'SELECT "documents_document"."id" FROM "documents_document" LEFT OUTER
> JOIN "documents_documenttype" ON
> ("documents_document"."document_type_id" =
> "documents_documenttype"."id") LEFT OUTER JOIN
> "documents_documentversion" ON ("documents_document"."id" =
> "documents_documentversion"."document_id") LEFT OUTER JOIN
> "metadata_documentmetadata" ON ("documents_document"."id" =
> "metadata_documentmetadata"."document_id") LEFT OUTER JOIN
> "documents_documentpage" ON ("documents_documentversion"."id" =
> "documents_documentpage"."document_version_id") LEFT OUTER JOIN
> "taggit_taggeditem" ON ("documents_document"."id" =
> "taggit_taggeditem"."object_id") LEFT OUTER JOIN "taggit_tag" ON
> ("taggit_taggeditem"."tag_id" = "taggit_tag"."id") LEFT OUTER JOIN
> "django_comments" ON ("documents_document"."id" =
> "django_comments"."object_pk") WHERE
> (UPPER("documents_documenttype"."name"::text) LIKE UPPER(%s)  OR
> UPPER("documents_documentversion"."mimetype"::text) LIKE UPPER(%s)  OR
> UPPER("documents_documentversion"."filename"::text) LIKE UPPER(%s)  OR
> UPPER("metadata_documentmetadata"."value"::text) LIKE UPPER(%s)  OR
> UPPER("documents_documentpage"."content"::text) LIKE UPPER(%s)  OR
> UPPER("documents_document"."description"::text) LIKE UPPER(%s)  OR
> (UPPER("taggit_tag"."name"::text) LIKE UPPER(%s)  AND
> "taggit_taggeditem"."content_type_id" = %s ) OR
> (UPPER("django_comments"."comment"::text) LIKE UPPER(%s)  AND
> "django_comments"."content_type_id" = %s )) ORDER BY
> "documents_document"."date_added" DESC'
> and scolds me for
> ERROR:  operator does not exist: integer = text
> LEFT OUTER JOIN "django_comments" ON ("documents_document"."id" =
> "django_comments"."object_pk")
> No operator matches the given name and argument type(s). You might
> need to add explicit type casts.
>
>

Hi!

just had the same problem... it seems the only issue regarding search with
postgresql is that the comments contrib app uses object_pk instead of object_id
for the GenericForeignKey.

If someone really wants to use postgresql before a permanent fix or new search
engine is available, it works if you paste the following hack at the end of
apps/dynamic_search/models.py:

from django.db import connection
if connection.vendor == 'postgresql':
    from django.db.models.sql.compiler import SQLCompiler
    orig_get_from_clause = SQLCompiler.get_from_clause
    def get_from_clause(self):
        result, extra = orig_get_from_clause(self)
        result = map(lambda s: s.replace('"django_comments"."object_pk"',
                        '"django_comments"."object_pk"::integer'), result)
        return result, extra
    SQLCompiler.get_from_clause = get_from_clause


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Mayan EDMS: 218] Re: Mayan EDMS v0.12 released!

VítorFigueiró
On 05-07-2012 05:07, Roberto Rosario wrote:
Wow!  Awesome!  I will include this in the next maintenance release for the 0.12 series.  Thanks a lot!

On Wednesday, July 4, 2012 5:47:22 PM UTC-4, vfigueiro wrote:
Roberto Rosario Gonzalez [hidden email] writes:

>
>
> Yes, Postgresql complains about some parts of the search code whereas MySQL
and SQLite work Ok.  This one of the reasons I'm switching Mayan to a dedicated
engine like Haystack, it is planned to be done during this development cycle
right when I finish the inital workflow app.
>
> On Mar 16, 2012 2:40 AM, "Сергей Глита"
[hidden email] wrote:
> Hi, Roberto!
> Search does not work for the field "comment"
> Maybe it's because pgsql
> Django sends the following query
> 'SELECT "documents_document"."id" FROM "documents_document" LEFT OUTER
> JOIN "documents_documenttype" ON
> ("documents_document"."document_type_id" =
> "documents_documenttype"."id") LEFT OUTER JOIN
> "documents_documentversion" ON ("documents_document"."id" =
> "documents_documentversion"."document_id") LEFT OUTER JOIN
> "metadata_documentmetadata" ON ("documents_document"."id" =
> "metadata_documentmetadata"."document_id") LEFT OUTER JOIN
> "documents_documentpage" ON ("documents_documentversion"."id" =
> "documents_documentpage"."document_version_id") LEFT OUTER JOIN
> "taggit_taggeditem" ON ("documents_document"."id" =
> "taggit_taggeditem"."object_id") LEFT OUTER JOIN "taggit_tag" ON
> ("taggit_taggeditem"."tag_id" = "taggit_tag"."id") LEFT OUTER JOIN
> "django_comments" ON ("documents_document"."id" =
> "django_comments"."object_pk") WHERE
> (UPPER("documents_documenttype"."name"::text) LIKE UPPER(%s)  OR
> UPPER("documents_documentversion"."mimetype"::text) LIKE UPPER(%s)  OR
> UPPER("documents_documentversion"."filename"::text) LIKE UPPER(%s)  OR
> UPPER("metadata_documentmetadata"."value"::text) LIKE UPPER(%s)  OR
> UPPER("documents_documentpage"."content"::text) LIKE UPPER(%s)  OR
> UPPER("documents_document"."description"::text) LIKE UPPER(%s)  OR
> (UPPER("taggit_tag"."name"::text) LIKE UPPER(%s)  AND
> "taggit_taggeditem"."content_type_id" = %s ) OR
> (UPPER("django_comments"."comment"::text) LIKE UPPER(%s)  AND
> "django_comments"."content_type_id" = %s )) ORDER BY
> "documents_document"."date_added" DESC'
> and scolds me for
> ERROR:  operator does not exist: integer = text
> LEFT OUTER JOIN "django_comments" ON ("documents_document"."id" =
> "django_comments"."object_pk")
> No operator matches the given name and argument type(s). You might
> need to add explicit type casts.
>
>

Hi!

just had the same problem... it seems the only issue regarding search with
postgresql is that the comments contrib app uses object_pk instead of object_id
for the GenericForeignKey.

If someone really wants to use postgresql before a permanent fix or new search
engine is available, it works if you paste the following hack at the end of
apps/dynamic_search/models.py:

from django.db import connection
if connection.vendor == 'postgresql':
    from django.db.models.sql.compiler import SQLCompiler
    orig_get_from_clause = SQLCompiler.get_from_clause
    def get_from_clause(self):
        result, extra = orig_get_from_clause(self)
        result = map(lambda s: s.replace('"django_comments"."object_pk"',
                        '"django_comments"."object_pk"::integer'), result)
        return result, extra
    SQLCompiler.get_from_clause = get_from_clause



Welcome :) congrats and thank you for sharing Mayan!
Loading...