Something strange on 3.5 branch.

Just display a customer http://localhost/dolibarrDev/htdocs/societe/soc.php?socid=1 a pop (like "confirm box") named "Adress" appears.

I try to find where it come from. It come from function show_contacts, of core/lib/company.lib, there is dialog adress display (without print with open php tag and close tag (the is normaly nothing like that in Dolibarr except in template), but i don't understand what is it for. I try to chek the history of this file without finding the "Why" there is this piece of code here. It seems to be a multi adress management...

Regards

Florian HENRY
florian.he...@open-concept.pro
+33 6 03 76 48 07
http://www.open-concept.pro
Twitter : @_Open_Concept_

Le 01/04/2014 16:20, Marcos García a écrit :
Hi:

Lots of improvements have been done in opensurvey module for 3.6 version. That module shouldn't have been released in 3.5 because there were some bugs and a lot of work to be done.

I think you guys should not waste lot of time in fixing the problem because in the next version you'll see lots of changes...

Regards,

    *Marcos García*

    marcos...@gmail.com <mailto:marcos...@gmail.com>



2014-04-01 16:04 GMT+02:00 [Kreiz IT]Cédric GROSS <c.gr...@kreiz-it.fr <mailto:c.gr...@kreiz-it.fr>>:

    Hello,

    I had a quick look on bug list :

    #1307: I tested every field on product, propel and invoice. Only
    product reference remove quote (single).

    Regarding double quote : Put a double quote in ref product lead to
    "Reference is needed" error when create a product.

    When modify a product : label and custom_code text is wiped out
    after double quote. I haven't tested more for propel and invoice

    #1311 : Is not really a bug as status was not shown by the past
    for supplier.

    #1312: I had a look on that but there 're lot of "_()" function
    and a lot of untranslated string. So it's surely an on-going work
    ? (eldy ?)

    #1319 : Don't reach to reproduce it with 3.5 github version

    #1322 : Don't reach to reproduce

    Now regarding #1317:

    There are several way to solve problem :

    -Deny delete if have child category

    -Move up child one level

    -Delete all child

    Does anyone have begin to work on this ?

    What is your think about solution ?

    Cedric

    *De :*dolibarr-dev-bounces+c.gross=kreiz-it...@nongnu.org
    <mailto:kreiz-it...@nongnu.org>
    [mailto:dolibarr-dev-bounces+c.gross
    <mailto:dolibarr-dev-bounces%2Bc.gross>=kreiz-it...@nongnu.org
    <mailto:kreiz-it...@nongnu.org>] *De la part de* Destailleur Laurent
    *Envoyé :* mardi 1 avril 2014 13:56
    *À :* ML Dolibarr dev
    *Objet :* [Dolibarr-dev] Dolibarr 3.5.2

    Hi Dolibarr dev.

    I plan to release a maintenance version of branch 3.5 this week-end.

    A lot of fix were fixed during devcamp. Some were annoying and i
    think there is enough to justify a new maintenance version.

    If you still have bug fixed on 3.5 branch waiting on your
    workspace, please push them on github so I can include them for
    3.5.2 otherwise it will be for 3.5.3 :-) (PS:only bug fixes of
    course for 3.5 branch).

    Note: For very old version (3.3 branch), a new maintenance version
    3.3.5 has been released. Announcement should appears on social
    networks in 24h.

--
    Laurent

    
------------------------------------------------------------------------------------

    Google+: https://plus.google.com/+LaurentDestailleur/

    Facebook: https://www.facebook.com/Destailleur.Laurent

    Twitter: http://www.twitter.com/eldy10


    _______________________________________________
    Dolibarr-dev mailing list
    Dolibarr-dev@nongnu.org <mailto:Dolibarr-dev@nongnu.org>
    https://lists.nongnu.org/mailman/listinfo/dolibarr-dev




_______________________________________________
Dolibarr-dev mailing list
Dolibarr-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev

_______________________________________________
Dolibarr-dev mailing list
Dolibarr-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev

Répondre à