« MyField/en » : différence entre les versions

De Documentations Patas-monkey
Aller à la navigation Aller à la recherche
Liam (discussion | contributions)
Page créée avec « |- | style="vertical-align:top;" | Background Color | style="vertical-align:top;" | Use the color picker to determine the background color of the myField. |- | style="vertical-align:top;" | Move | style="vertical-align:top;" | Enter -1 to move the menu tab to the left, 1 to move the right. |- | style="vertical-align:top;" | Redirect URL | style="vertical-align:top;" | Enter the URL of the page that will be displayed when the menu tab is clicked. If this field is... »
FuzzyBot (discussion | contributions)
Mise à jour pour être en accord avec la nouvelle version de la source de la page
 
(63 versions intermédiaires par un autre utilisateur non affichées)
Ligne 17 : Ligne 17 :
The module is configured from the module administration page accessible via the menus '''Home > Configuration > Modules''' by clicking on the [[file:doli-setup.png]] icon or the [[file:doli-setup-old.png]] icon at the end of the line.
The module is configured from the module administration page accessible via the menus '''Home > Configuration > Modules''' by clicking on the [[file:doli-setup.png]] icon or the [[file:doli-setup-old.png]] icon at the end of the line.


[[file:myfield_Configuration.png|800px]]
[[file:myfield_Configuration_en.png|800px]]


<span id="Page_de_configuration_du_module"></span>
<span id="Page_de_configuration_du_module"></span>
Ligne 59 : Ligne 59 :
==== Support Information ====
==== Support Information ====
At the bottom of the configuration page you will find technical information related to your installation. This technical information will be useful and may be requested if you encounter a bug in using the module:
At the bottom of the configuration page you will find technical information related to your installation. This technical information will be useful and may be requested if you encounter a bug in using the module:
[[file:Myfield_Technical-information.png||800px]]
[[file:Myfield_Technical-information_en.png||800px]]


===Permissions===
===Permissions===
Ligne 73 : Ligne 73 :
====User and group permissions====
====User and group permissions====
{| class="wikitable"
{| class="wikitable"
| [[file:myfield-Permissions-Utilisateur.png|600px]]
| [[file:myfield-Permissions-utilisateur_en.png|600px]]
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Access to the module's features can be restricted to users and groups, from their profile then Permissions tab, according to the permissions opposite
Access to the module's features can be restricted to users and groups, from their profile then Permissions tab, according to the permissions opposite
|}
|}


<div class="mw-translate-fuzzy">
====Default Permissions====
====Default Permissions====
{| class="wikitable"
{| class="wikitable"
| [[file:myfield-Permissions-defaut.png|600px]]
| [[file:myfield-Permissions-defaut_en.png|600px]]
| style="vertical-align:top;" |
| style="vertical-align:top;" |
The default permissions ('''Home > Configuration > Security > Default Permissions'''), granted to any user created after the installation of the module, if he is not added to a group, are the following
The default permissions ('''Home > Users & Group > Choose between Users or Group > Select Permissions'''), granted to any user created after the installation of the module, if he is not added to a group, are the following
|}
|}
</div>


<span id="Démarrage"></span>
<span id="Démarrage"></span>
Ligne 126 : Ligne 128 :
The page for creating a menu-type myField is accessible from the secondary menu link '''Patas-tools > MyField > New myMenu.'''
The page for creating a menu-type myField is accessible from the secondary menu link '''Patas-tools > MyField > New myMenu.'''


[[File:Myfield-Page-creation-menu.png|800px]]
[[File:Myfield-Page-creation-menu_en.png|800px]]


{|
{|
Ligne 189 : Ligne 191 :
Let's customize the ''Home'' menu.
Let's customize the ''Home'' menu.


[[file:myfield-Param-menu-accueil.png|600px]]
[[file:myfield-Param-menu-accueil_en.png|600px]]


[[file:Myfield-menu-resultat.png|600px]]
[[file:Myfield-menu-resultat_en.png|600px]]


====Example of customizing a menu and a secondary menu entry====
====Example of customizing a menu and a secondary menu entry====
Let's customize the Commercial Proposals secondary menu and the New Proposal secondary menu entry.
Let's customize the Commercial Proposals secondary menu and the New Proposal secondary menu entry.


[[file:myfield-Param-menu-secondaire.png|600px]]  
[[file:myfield-Param-menu-secondaire_en.png|800px]]  


[[file:myfield-Param-entree-menu-secondaire.png|600px]]  
[[file:myfield-Param-entree-menu-secondaire_en.png|800px]]  


{{Note|The secondary menu entry will be moved down one rank with the code -1 in the Move field of its record}}
{{Note|The secondary menu entry will be moved down one rank with the code -1 in the Move field of its record}}
Ligne 204 : Ligne 206 :


{| class="wikitable"
{| class="wikitable"
| [[file:Myfield-entree-menu-secondaire.png]]
| [[file:Myfield-entree-menu-secondaire_en.png]]
| style="vertical-align:top;" |
| style="vertical-align:top;" |
  rather than
  rather than
| [[file:Myfield-menu-secondary.png]]
| [[file:Myfield-menu-secondaire_en.png]]
|}
|}


Ligne 217 : Ligne 219 :
''Add to the label the secondary menu: Commercial proposals#List''
''Add to the label the secondary menu: Commercial proposals#List''


[[file:myfield_Liste-param.png|600px]]  
[[file:myfield_Liste-param_en.png|600px]]  


| style="vertical-align:top;" |
| style="vertical-align:top;" |
To get   
To get   


[[file:myfield_Liste-param-menu.png]]
[[file:myfield_Liste-param-menu_en.png]]
|}
|}


Ligne 229 : Ligne 231 :
The myField creation page is accessible from the secondary menu link '''Patastools > MyField > New MyTab'''.
The myField creation page is accessible from the secondary menu link '''Patastools > MyField > New MyTab'''.


[[file:myfield-Page-creation-onglet.png|600px]]
[[file:myfield-Page-creation-onglet_en.png|600px]]


{|
{|
Ligne 303 : Ligne 305 :
Let's customize the tab sheet of the element sheets.
Let's customize the tab sheet of the element sheets.


[[file:myfield-Param-onglet-fiche.png|800px]]  
[[file:myfield-Param-onglet-fiche_en.png|800px]]  


<div lang="fr" dir="ltr" class="mw-content-ltr">
The sheet then becomes
La fiche devient alors
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[file:myfield-Natif-fiche_en.png|800px]]
[[file:myfield-Natif-fiche.png|800px]]  
{{Note|If the tab is active, the color will be displayed on its edges}}
{{Note|Si l'onglet est actif, la couleur sera affichée sur ses bords}}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
===Fields===
===Champs===
====Creating myField====
====Création du myField====
The myField creation page is accessible from the secondary menu link '''Patastools > MyField > New MyField'''.
La page de création d'un myField est accessible depuis le lien de menu secondaire '''Patastools > MyField > Nouveau MyField'''.
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[file:myfield-Page-creation_en.png|600px]]  
[[file:myfield-Page-creation.png|600px]]
</div>




<div lang="fr" dir="ltr" class="mw-content-ltr">
{|
{|  
| style="vertical-align:top;width:50%;" |
| style="vertical-align:top;width:50%;" |
{| class="wikitable"
{| class="wikitable"
| style="vertical-align:top;width:25%;" |
| style="vertical-align:top;width:25%;" |
Type de myField
myField Type
| style="vertical-align:top;" |  
| style="vertical-align:top;" |
le champ automatiquement rempli en fonction du lien de menu sur lequel vous avez cliqué.
the field automatically filled in based on the menu link you clicked.
|-
|-
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Libellé natif
Native Label
| style="vertical-align:top;" |  
| style="vertical-align:top;" |
saisissez ici le libellé natif du champ tel qu'il est affiché à l'écran.
enter here the native label of the field as it is displayed on the screen.
|-
|-
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Contexte d'activation 
Activation Context
| style="vertical-align:top;" |  
| style="vertical-align:top;" |
le contexte d'activation permet de limiter l'action des myFields sur les seuls champs des pages comportant le contexte indiqué ici.  
the activation context allows you to limit the action of myFields to only the fields of the pages with the context indicated here.
Si aucun contexte n'est saisi, les modifications apportées à l'onglet par le myfield s'appliqueront à tous les champs du même libellé de toutes les fiches.
If no context is entered, changes made to the tab by the myfield will apply to all fields with the same label on all records.
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[#Activation context|List of main contexts]]
[[#Contexte d'activation|Liste des principaux contexte ]]
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
|-
|-
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Texte de remplacement
Replacement text
| style="vertical-align:top;" |  
| style="vertical-align:top;" |
texte de votre choix qui sera affiché à la place du libellé natif.
text of your choice that will be displayed instead of the native label.
|-
|-
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Auteur
Author
| style="vertical-align:top;" |  
| style="vertical-align:top;" |
le nom du créateur du myField
the name of the creator of the myField
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
|}
|}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
| style="vertical-align:top;" |
| style="vertical-align:top;" |  
{| class="wikitable"
{| class="wikitable"
| style="vertical-align:top;width:25%;" |
| style="vertical-align:top;width:25%;" |
Affichage
Display
| style="vertical-align:top;" |  
| style="vertical-align:top;" |
*Visible : le champ sera affiché. Il s'agit du fonctionnement standard de Dolibarr.
*Visible: the field will be displayed. This is the standard operation of Dolibarr.
*Invisible : le champ sera absent des fiches
*Invisible: the field will be absent from the cards
*Caché : le champ sera absent des fiches mais pourra être affiché (Show/Hide).  
*Hidden: the field will be absent from the cards but can be displayed (Show/Hide).
{{Note|sur les dernières versions du module, (Show/Hide) n'est plus employé, il faut à présent cliquer sur le numéro de version de Dolibarr (en haut à droite)|warn}}
{{Note|on the latest versions of the module, (Show/Hide) is no longer used, you must now click on the Dolibarr version number (top right)|warn}}
|-
| style="vertical-align:top;" |
Background color
| style="vertical-align:top;" |
use the color selector to determine the background color of the myField.
|-
|-
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Couleur de fond
Move
| style="vertical-align:top;" |  
| style="vertical-align:top;" |
utilisez le sélecteur de couleur pour déterminer la couleur de fond du myField.
enter 1 to move up one field, -1 to move down one field.
|-
|-
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Déplacement
Default value
| style="vertical-align:top;" |  
| style="vertical-align:top;" |  
saisissez 1 pour remonter d'un champ, -1 pour descendre.
 
|-
|-
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Valeur par défaut
Input field size
| style="vertical-align:top;" |
| style="vertical-align:top;" |
</div>
to be defined according to your needs. If left blank, the native value of the field is kept.
 
<div lang="fr" dir="ltr" class="mw-content-ltr">
|-
|-
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Taille du champ de saisie
Mandatory:
| style="vertical-align:top;" |  
| style="vertical-align:top;" |
à définir selon vos besoins. Si laissé vide, la valeur native du champ est conservée.
check this box to make entering values ​​in the field mandatory to save the creation or modifications of the page
{{Note|The control of the field in creation and modification is only carried out if you enter the edition of the field itself|warn}}
|-
|-
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Obligatoire :
Input mask
| style="vertical-align:top;" |  
| style="vertical-align:top;" |
cochez cette case pour rendre la saisie de valeurs dans le champ obligatoire pour enregistrer la création ou les modifications de la page
the input mask can be configured with the following characters:
{{Note|Le contrôle du champ en création et modification n'est effectué que si l'on rentre en édition du champ lui-même|warn}}
*a for a letter (A-Z,a-z)
*9 for a number (0-9)
*for an alphanumeric character (A-Z,a-z,0-9)
:You can add the characters you want to the field to make up your mask. For example, if you want to add an international code to the phone field, the mask will be: +0099-(9)999999999
*UPPERCASE to force uppercase input.
*LOWERCASE to force lowercase input.
|-
|-
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Masque de saisie
Display request
| style="vertical-align:top;" |
le masque de saisie est paramétrable avec les caractères suivants :
*a pour une lettre (A-Z,a-z)
*9 pour un chiffre (0-9)
*pour un caractère alphanumérique (A-Z,a-z,0-9)
:Vous pouvez ajouter dans le champ les caractères que vous souhaitez pour constituer votre masque. Par exemple, si vous souhaitez ajouter un indicatif international au champ téléphone, le masque sera : +0099-(9)999999999
*UPPERCASE pour forcer la saisie en majuscule.
*LOWERCASE pour forcer la saisie en minuscule.
|-
| style="vertical-align:top;" |
| style="vertical-align:top;" |
Requête d'affichage
See Operation section
| style="vertical-align:top;" |
Voir section Fonctionnement
|}
|}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
|}
|}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
{{Note|Moving a field in a form is only done within its table. It is therefore possible to move a field up or down, but not to change its column}}
{{Note|Le déplacement d'un champ d'une fiche n'est effectué qu'au sein de son tableau. Il est donc possible de remonter ou descendre un champ, mais pas de le changer de colonne}}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
Following the creation of a field type myField, it will be necessary to define the access rights to the myFields by user groups from the secondary menu link of the same name (See section Configuring access rights).
Suite à la création d'un myField de type champ, il sera nécessaire de définir les droits d'accès aux myFields par groupes d'utilisateurs depuis le lien de menu secondaire du même nom (Voir section Configuration des droits d'accès).
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
====Example of customizing a field====
====Exemple de personnalisation d'un champ====
Let's customize the field ''Id. prof. 2 (SIRET)'' of third-party files.
Personnalisons le champ ''Id. prof. 2 (SIRET)'' des fiches de tiers.
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
{| class="wikitable"
{| class="wikitable"
|- style="vertical-align:top;"
|- style="vertical-align:top;"
| [[file:myfield_Param-champ.png|600px]]
| [[file:myfield_Param-champ_en.png|600px]]
| Le champ a été paramétré en tant qu'invisible avec un masque de saisie de chiffres (999 999 999 99999)
| The field has been set to invisible with a number input mask (999 999 999 99999)  
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
|- style="vertical-align:top;"
|- style="vertical-align:top;"
| [[file:Myfield-champ.png|600px]]
| [[file:Myfield-champ_en.png|600px]]  
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[file:myfield-Masque_en.png]]
[[file:myfield-Masque.png]]
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
|
|
En cliquant sur le lien Show/Hide au-dessus du tableau, le champ sera affiché selon les paramètres enregistrés sur la fiche du myField
By clicking on the Show/Hide link above the table, the field will be displayed according to the settings saved on the myField sheet
</div>




<div lang="fr" dir="ltr" class="mw-content-ltr">
When editing the field, the mask will be activated and will only allow the predefined entry and its completion checked (made mandatory) to prevent the page from being saved without it being filled in.
Lors de l'édition du champ, le masque sera activé et ne permettra que la saisie prédéfinie et sa complétion vérifiée (rendu obligatoire) pour empêcher l'enregistrement de la page sans qu'il ne soit rempli.
|}
|}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
===Lists===
===Listes===
It is possible to modify the fields of the native lists of dolibarr (the one with a field selection icon at the end of the list)
Il est possible de modifier les champs des listes natives de dolibarr (celle avec une icone de sélection de champs en bout de liste)
</div>




<div lang="fr" dir="ltr" class="mw-content-ltr">
====Creating myField====
====Création du myField====
List myfields allow you to limit the display of fields.
Les myfields de liste permettent de limiter l'affichage de champs.
It is necessary to open the list page to retrieve information specific to this type of myField
il est nécessaire d'ouvrir la page de liste pour récupérer des informations propre à ce type de myField  
* the activation context
* le contexte d'activation
* the untranslated label of the field
* le libellé non traduit du champs
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
====Example of setting====
====Exemple de paramétrage====
We will modify the "Third party" column on the list of interventions
Nous allons modifier la colonne "Tiers" sur la liste des interventions
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[file:Myfield-masque-tiers_en.png|600px]]
[[file:Myfield-masque-tiers.png|600px]]
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
Depending on the permissions, the field will also be inaccessible in the field selector.
Selon les habilitations, le champs sera aussi inaccessible dans le sélecteur de champs.
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[file:myfield_Liste-contrats_en.png|600px]]
[[file:myfield_Liste-contrats.png|600px]]
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
{{Note|If you make a list myField invisible, it will be invisible to all users. To hide it only from one or more groups of users, leave it visible and then add access rights!}}
{{Note|Si vous rendez un myField de liste invisible, il sera invisible de tous les utilisateur. Pour le cacher seulement à un ou des groupes d'utilisateurs, laissez le visible et jouter ensuite avec les droits d'accès !}}
</div>






<div lang="fr" dir="ltr" class="mw-content-ltr">
=== Buttons ===
=== Boutons ===
It is possible to modify the buttons present on the dolibarr files
Il est possible de modifier les boutons présent sur les fiches de dolibarr
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
====Creation of myField====
====Création du myField====
Button myfields allow you to make the button invisible, replace the label, the url associated with the button and make its access visible according to the result of an SQL query
Les myfield de boutons permettent de rendre invisible bouton, remplacer le libellé, l'url associé au bouton et de rendre son accès visible selon le résultat d'une requete SQL
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[file:myfield-creation-bouton_en.png|600px]]
[[file:myfield-creation-bouton.png|600px]]
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
{{Note|With the native Dolibarr theme, the button label is capitalized, so you must use the original text that you retrieve with the right click and the inspect menu.}}
{{Note|Avec le thème natif de Dolibarr, le libellé du bouton est mis en majuscule, il faut donc utiliser le texte d'origine que l'on récupère avec le click droit et le menu inspecter.}}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
=Conditional display SQL query=
=Requête SQL d'affichage conditionnel=
The processing query will condition the display of the fields according to the correspondence of the object to the query. It is then possible, for example, to display different fields depending on whether the object is a product or a service.
La requête de traitement va conditionner l'affichage des champs selon la correspondance de l'objet à la requête. Il est alors possible, par exemple, d'afficher des champs différents selon que l'objet est un produits ou un service.
It is possible to transmit two values ​​as parameters:
Il est possible de transmettre en paramètre deux valeurs :
* #ID#: the id of the main object of the page
* #ID# : l'id de l'objet principale de la page  
* #USERID#: the id of the active user
* #USERID# : l'id de l'utilisateur actif
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
<span id="Fonctionnement"></span>
==Fonctionnement==
==How it works==
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
Enter here the display query applicable to the fields in the following example:
Saisissez ici la requête d'affichage applicable au champs sur l'exemple suivant :
</div>


  <div lang="fr" dir="ltr" class="mw-content-ltr">
  #SEL# allows you to replace the SELECT of the SQL query which will be blocked by Dolibarr's native security (SQL Injection)
#SEL# permet de remplacer le SELECT de la requête SQL qui sera bloqué par la sécurité native de Dolibarr (SQL Injection)
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
''#SEL# IF(fk_product_type=1, 1, 0) AS `read`, IF(fk_product_type=1, 1, 0) AS `write` FROM llx_product WHERE rowid=#ID#; ''
''#SEL# IF(fk_product_type=1, 1, 0) AS `read`, IF(fk_product_type=1, 1, 0) AS `write` FROM llx_product WHERE rowid=#ID#; ''
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
read allows you to authorize or not the global display of the field
read permet d'autoriser ou non l'affichage globale du champ
write allows you to authorize or not its modification (not necessary in the case of a button or a tab...)
write permet d'autoriser ou non sa modification (pas nécessaire dans le cas d'un bouton un un onglet...)
 
</div>
If the value is 0, the field is hidden, otherwise it is displayed
Be careful, if we leave the field parameter hidden, it will not appear regardless of the value


<div lang="fr" dir="ltr" class="mw-content-ltr">
==Example==
Si la valeur est à 0, le champs est caché, dans le cas contraire il est affiché
With the following myfield
Attention, si on laisse le paramètre du champs à caché, il n'apparaitra pas quel que soit la valeur
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[file:myfield_Creation_requete_en.png|800px]]
==Exemple==
Avec le myfield suivant
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
{| class="wikitable"
[[file:myfield_Creation_requete.png|800px]]
|- style="vertical-align:top;"
</div>
| We obtain the following sheet on a '''product'''
[[file:myfield_Creation_requete_result_en.png|400px]]
| While on the sheet of a '''service'''
[[file:myfield_Creation_requete-fiche_en.png|400px]]


<div lang="fr" dir="ltr" class="mw-content-ltr">
{| class="wikitable"
|- style="vertical-align:top;"
| On obtient la fiche suivante sur un '''produit'''
[[file:myfield_Creation_requete_result.png|400px]]
| Tandis que sur la fiche d'un '''service'''
[[file:myfield_Creation_requete-fiche.png|400px]]
|}
|}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
=Setting access rights to myFields, tabs and menus=
=Paramétrage des droits d'accès aux myFields, tabs et menus=
==Configuring access rights==
==Configuration des droits d'accès==
As an administrator user, all myFields are visible to you.
En tant qu'utilisateur administrateur, tous les myFields vous sont visibles.
{{Note|On the MyField module home page, the application of customizations is disabled}}
{{Note|Sur la page d'accueil du module MyField, l'application des personnalisations est désactivée}}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
If you have not defined any user groups, myfields are displayed on all users' interfaces.
Si vous n'avez pas défini de groupes utilisateurs, les myfields sont affichés sur les interfaces de tous les utilsiateurs.
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
From the secondary menu entry '''Patas-Tools > MyField > tab access rights''', configure the accesses of the user groups:
Depuis l'entrée de menu secondaire '''Patas-Tools > MyField > droits d'accès aux onglets''', paramétrez les accès des groupes d'utilisateurs :
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[file:myfield-Droits-d-acces_en.png|600px]]
[[file:myfield-Droits-d-acces.png|600px]]
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
There are four access rights:
Il existe quatre droits d'accès :
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
{| class="wikitable"
{| class="wikitable"  
|- style="vertical-align:top;"
|- style="vertical-align:top;"  
| [[File:lecture-off.png]] Access blocked
| [[File:lecture-off.png]] Bloqué en accès
[[file:lecture-on.png]] Access read
[[file:lecture-on.png]] Accès en lecture
| [[file:modif-of.png]] Edit blocked
| [[file:modif-of.png]] Bloqué en modification
[[file:modif-on.png]] Edit access
[[file:modif-on.png]] Accès en modification
|}
|}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
==Behavior according to access rights==
==Comportement selon les droits d'accès==
===Blocked in access ([[file:lecture-off.png]]) ===
===Bloqué en accès ([[file:lecture-off.png]]) ===
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
{| class="wikitable"
{| class="wikitable"  
|- style="vertical-align:top;"
|- style="vertical-align:top;"  
| [[file:myfield-User-lecture-_en.png|600px]]
| [[file:myfield-User-lecture-.png|600px]]
| The field will be hidden from users in the group. They will not be able to view it
| Le champ sera caché aux utilisateurs du groupe. Ils ne pourront pas l'afficher
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
the ''Show/Hide'' link will not be active
le lien ''Show/Hide'' ne sera pas actif
|}
|}
===Accès en lecture mais bloqué en modification ([[file:lecture-on.png]][[file:modif-of.png]]) ===
===Read access but blocked from editing ([[file:lecture-on.png]][[file:modif-of.png]]) ===
{| class="wikitable"  
{| class="wikitable"
|- style="vertical-align:top;"  
|- style="vertical-align:top;"
| [[file:myfield-User-lecture-.png|600px]]
| [[file:myfield-User-lecture-_en.png|600px]]
| Les utilisateurs du groupe pourront afficher le champ, mais ne pourront pas en modifier le contenu.
| Users in the group will be able to view the field, but will not be able to edit its content.
|}
|}
===Accès en lecture et Accès en modification ([[file:lecture-on.png]][[file:modif-on.png]]) ===
===Read access and Edit access ([[file:lecture-on.png]][[file:modif-on.png]]) ===
{| class="wikitable"  
{| class="wikitable"
|- style="vertical-align:top;"  
|- style="vertical-align:top;"
| [[file:myfield-User-lecture+-modif+.png|600px]]
| [[file:myfield-User-lecture+-modif+_en.png|600px]]
|  
|
Les utilisateurs du groupe pourront afficher le champ et le modifier si leurs permissions de groupe ou d'utilisateur le leur permettent. Les paramètres du champ s'appliquent alors (obligatoire, masque de saisie,...)
Users in the group will be able to view and edit the field if their group or user permissions allow them to do so. The field settings then apply (mandatory, input mask, etc.)
|}
|}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
=Other features=
=Autres fonctionnalités=
==Importing myFields==
==Import des myField==
It is possible to save a list of myfields and their settings by importing an XML file.
Il est possible d'enregistrer une liste de myfields et leurs paramétrages en important un fichier XML.
From the '''Patas-M Tools > MyField > Import a tab''' page, paste the XML file into the input area and click on the '''Start import''' button.
Depuis la page '''Outils Patas-M > MyField > Importer un onglet''', collez le fichier XML dans la zone de saisie et cliquez sur le bouton '''Lancer l'importation'''.
{{Note|If you check the Overwrite previous data box, your list of myfields will be limited to those present in the file you are importing|warn}}
{{Note|Si vous cochez la case Écraser les données précédentes, votre liste de myfields se résumera à ceux présent dans le ficher que vous importez|warn}}
Then configure the users' access rights to the myField.
Paramétrer ensuite les droits d'accès des utilisateurs au myField.
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
==Activation context==
==Contexte d'activation==
A list of all available contexts is present on the dolibarr wiki:
Une liste de tous les contextes disponible est présent sur le wiki de dolibarr:  
https://wiki.dolibarr.org/index.php?title=Hooks_System#List_of_Contexts_available_in_Dolibarr
https://wiki.dolibarr.org/index.php?title=Syst%C3%A8me_de_Hooks#Liste_des_Contexts_disponibles_dans_Dolibarr
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
some of the most common
quelque uns des plus courants
{|
{|  
|
|  
{| class="wikitable"
{| class="wikitable"
|- style="background-color:orange; font-weight:bold;"
|- style="background-color:orange; font-weight:bold;"
| Fiche
| Card
| Contexte
| Context
|-
|-
| Adhérent
| Member
| membertypecard
| membertypecard
|-
|-
| Catégories
| Categories
| categorycard
| categorycard
|-
|-
| Commandes
| Orders
| ordercard
| ordercard
|-
|-
| Commande fournisseur
| Supplier order
| ordersuppliercard
| ordersuppliercard
|-
|-
Ligne 679 : Ligne 579 :
| contactcard
| contactcard
|-
|-
| Contrat
| Contract
| contractcard
| contractcard
|-
|-
| Don
| Donation
| doncard
| doncard
|-
|-
| Entrepôt
| Warehouse
| warehousecard
| warehousecard
|-
|-
| Expédition
| Shipping
| expeditioncard
| expeditioncard
|-
|-
| Facture client
| Customer invoice
| invoicecard
| invoicecard
|-
|-
| Facture fournisseur
| Supplier invoice
| suppliercard
| suppliercard
|}
|}  
</div>




<div lang="fr" dir="ltr" class="mw-content-ltr">
| style="vertical-align:top;" |
| style="vertical-align:top;" |  
{| class="wikitable"
{| class="wikitable"
|- style="background-color:orange; font-weight:bold;"
|- style="background-color:orange; font-weight:bold;"
| Fiche
| Sheet
| Contexte
| Context
|-
|-
| Intervention
| Intervention
| interventioncard
| interventioncard
|-
|-
| Livraison
| Delivery
| deliverycard
| deliverycard
|-
|-
| Note de frais
| Expense report
| tripandexpensecard
| tripandexpensecard
|-
|-
| Produit
| Product
| productcard
| productcard
|-
|-
| Projet
| Project
| projectcard
| projectcard
|-
|-
| Proposition commerciale
| Commercial proposal
| propalcard
| propalcard
|-
|-
| Règlement client
| Customer payment
| paiementcard
| paymentcard
|-
|-
| Règlement fournisseur
| Supplier payment
| paymentsupplier
| paymentsupplier
|-
|-
| Salaire
| Salary
| salarycard
| salarycard
|-
|-
| Tache
| Task
| projecttaskcard
| projecttaskcard
|-
|-
| Tiers
| Third party
| thirdpartycard
| thirdpartycard
|-
|-
| Utilisateur
| User
| usercard
| usercard
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
|}
|}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
|}
|}
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
=Frequently Asked Questions=
=Questions fréquentes=
== General ==
== Général ==
This chapter lists the difficulties encountered with the module. You will therefore find answers to its use.
Ce chapitre répertorie les difficultés rencontrées avec le module. Vous y trouverez donc des éléments de réponse quant à son utilisation.
If you encounter an error other than those described below when using this module:
Si vous rencontrez une autre erreur que celles décrites ci-dessous lors de l'utilisation de ce module :
#Disable and reactivate the module,
#Désactivez et réactivez le module,
#Check on the ChangeLog if a new version has been published,
#Vérifier sur le ChangeLog si une nouvelle version a été publiée,
#Re-install/update the module,
#-installez/mettez à jour le module,
#Check that replacing native Dolibarr files is not necessary for the module to work properly.
#Vérifiez que le remplacement de fichiers natifs de Dolibarr ne soit pas nécessaire au bon fonctionnement du module.
#Check that no incompatibility with another module is indicated. If necessary, follow our recommendations.
#Vérifiez qu'aucune incompatibilité avec un autre module ne soit indiquée. Le cas échéant, suivez nos préconisations.
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
If, despite these manipulations, the error persists, contact us using the dedicated form (http://docs.patas-monkey.com/support/).
Si, malgré ces manipulations, l'erreur persiste, contactez-nous en utilisant le formulaire dédié (http://docs.patas-monkey.com/support/).
This form is the preferred contact method for any difficulty of use or bug report. Also, we thank you for not multiplying the exchange channels for the same object.
Ce formulaire est le mode de contact à privilégier pour toute difficulté d'utilisation ou remontée de bug. Aussi, nous vous remercions de ne pas multiplier les canaux d'échange pour un même objet.
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
== Displaying a message at the top of Dolibarr pages==
== Affichage d'un message en haut des pages de Dolibarr==
If your Dolibarr pages display a message similar to the following image, it is not an error message, but the display of the contexts of the current page. To no longer see these lines displayed, disable the display of the context
Si vos pages de Dolibarr affichent un message semblable à l'image suivante, il ne s'agit pas d'un message d'erreur, mais de l'affichage des contextes de la page courante. Pour ne plus voir ces lignes affichées, désactivez l'affichage du contexte
(see Configuration).
(voir Configuration).
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[file:Myfield-Message-contexte.png]]
[[file:Myfield-Message-contexte.png]]
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
==Ordering error message==
==Message erreur d'ordonnancement==
Some pages of some versions of Dolibarr have an error in their code preventing the correct application of field customization. MyField allows you to identify them in order to correct them.
Certaines pages de certaines versions de Dolibarr présentent un erreur dans leur code empêchant la bonne application de la personnalisation des champs. MyField permet de les identifier pour les corriger.
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
The error message is displayed at the bottom of the page and is as follows:
Le message d'erreur s'affiche en bas de page et est le suivant
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[file:myfield_Erreur-dbclose-message.png]]  
[[file:myfield_Erreur-dbclose-message.png]]
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
Using the URL of the page, open the Dolibarr core file to edit it. For example, if the page containing the message is ''http://.../htdocs/custom/myField/admin/extrafields.php'', successively open the folders ''htdocs'', ''custom'', ''myField'', ''admin'' and open the file ''extrafields.php''.
En vous aidant de l'URL de la page, ouvrez le fichier du noyau de Dolibarr pour le modifier. Par exemple, si la page qui comporte le message est ''http://.../htdocs/custom/myField/admin/extrafields.php'', ouvrez successivement les dossiers ''htdocs'', ''custom'', ''myField'', ''admin'' et ouvrez le fichier ''extrafields.php''.
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
The error comes from the inversion of the lines ''llxFooter();'' and ''$db->close();'' at the end of the file.
L'erreur vient de l'inversion des lignes ''llxFooter();'' et ''$db->close();'' en fin de fichier.
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
{| class="wikitable" style="width:60%;"
{| class="wikitable" style="width:60%;"  
|- style="vertical-align:top;"
|- style="vertical-align:top;"  
| Edit the page code to get
| Modifiez le code de la page pour obtenir
[[file:Erreur-dbclose-correction.png]]
[[file:Erreur-dbclose-correction.png]]
| au lieu de
| instead of
</div>


<div lang="fr" dir="ltr" class="mw-content-ltr">
[[file:Erreur-dbclose.png]]
[[file:Erreur-dbclose.png]]
|}
|}
==Multicompany==
==Multicompany==
Avec le module multicompany, il convient d'activer le module sur chaque entité
With the multicompany module, it is necessary to activate the module on each entity
</div>

Dernière version du 5 novembre 2025 à 18:23

The myField module allows you to customize the labels of menus, tabs, buttons, fields of Dolibarr cards and lists.

You can choose the label, color and access of your menus, buttons, tabs and fields of cards and lists yourself

Presentation

Depending on the type of myfield (fields of a form, list, tab, ...), several other options can be applied to the fields of the forms such as a background color, display/hide them, add an input mask, input in uppercase ...

The combined set of user permissions and myFields access rights allows you to configure user access to the view of fields, their content and their modification.

MyField also allows you to hide menus from groups of users and change their destination URL.

Settings

The module is configured from the module administration page accessible via the menus Home > Configuration > Modules by clicking on the icon or the icon at the end of the line.

Module Configuration Page

Activating the context for development

MyField allows you to display on certain Dolibarr pages the contexts that can be used to limit the customization actions of myFields. These contexts will be useful when creating myFields to limit the action of the module to only the pages that have in their code the context indicated on the myField sheet. Configuring the display of contexts on your pages will allow you to identify them to best configure your myfields.

Enabling the display of contexts results in messages like the one opposite

Administrators are above access rules

You can also choose to disable the use of access rights for the administrator user.

If this setting is enabled, the administrator will see, outside of any group, the myfields in operation.

Background color of input areas

By default, input areas in dolibarr are transparent, which does not help readability It is possible to change the background color of input areas

Default button color

There are three types of buttons in Dolibarr:

  • Buttons associated with an action
  • Disabled buttons
  • Buttons performing a deletion

myField allows you to change the color of these

Replacing native buttons

MyField allows replacing standard Dolibarr buttons with icons.

instead of

Support Information

At the bottom of the configuration page you will find technical information related to your installation. This technical information will be useful and may be requested if you encounter a bug in using the module:

Permissions

Access to the module's features can be restricted to existing users and groups or those created after the module is installed.

Click on the – to add a permission.

A granted permission is symbolized by a green check mark ().

Warning: there are other settings that can impact access to fields, especially when using an administrator account


User and group permissions

Access to the module's features can be restricted to users and groups, from their profile then Permissions tab, according to the permissions opposite

Default Permissions

The default permissions (Home > Users & Group > Choose between Users or Group > Select Permissions), granted to any user created after the installation of the module, if he is not added to a group, are the following

Startup

MyField features are accessible from the Patastools main menu tab. Your secondary menu then presents the following menu entries:

MyField The main entry displays a list of all myFields in your environment

New mf Field
New mf Tab
New mf Tab
New mf List
New mf Menu
New mf Button

These entries will display the page for creating a new myField according to its type:
  • form field
  • tab
  • button
  • list fields
  • menu
List of elements This entry will also display the list of myFields saved on your environment
Access rights to elements This page will allow you to configure the authorizations of user groups to the features of MyFields, tabs and menus.
Import XML This entry will display a page to copy an import file of a myfield in XML format.

Customizations

Menus

Creating the myField

The page for creating a menu-type myField is accessible from the secondary menu link Patas-tools > MyField > New myMenu.

myField Type

the field automatically filled in based on the menu link you clicked to display this creation page (menu).

Native Label

enter here the native label of the menu as it is displayed on your interface.

Menu Type

select from the drop-down list the type of menu you want to customize depending on whether it is a main menu, a secondary menu or a secondary menu entry.

Replacement text

text of your choice that will be displayed instead of the native label.

Author

the name of the creator of the myField

Display

  • Visible: the field will be displayed. This is the standard operation of Dolibarr.
  • Invisible: the field will be absent from the cards
  • Hidden: the field will be absent from the cards but can be displayed (Show/Hide).

Background color

use the color selector to determine the background color of the field.

Move

enter -1 to move the menu tab to the left, 1 to the right.

Redirect URL

Enter here the URL of the page that will be displayed when clicking on the menu tab. If this field is left blank, the native URL of the menu will be kept.

Following the creation of a myField, it will be necessary to define the access rights by user groups from the secondary menu link of the same name (See further)

Example of customizing a main menu

Let's customize the Home menu.

Example of customizing a menu and a secondary menu entry

Let's customize the Commercial Proposals secondary menu and the New Proposal secondary menu entry.

The secondary menu entry will be moved down one rank with the code -1 in the Move field of its record

Following the application of these two customizations, the secondary menu becomes:

rather than

Special case of secondary menu entries "List"

To differentiate secondary menu entries of the same name, enter the top-level menu to which they are attached separated by a hash mark (#):

Add to the label the secondary menu: Commercial proposals#List

To get

Tabs

Creating the myField tab

The myField creation page is accessible from the secondary menu link Patastools > MyField > New MyTab.

myField Type

the field automatically filled in based on the menu link you clicked.

Native Label

enter here the native label of the menu as it is displayed on the screen.

Activation Context

The activation context allows you to limit the action of myFields to only the fields of the pages with the context indicated here.

Attention, for tabs, the context corresponds to the tabTitleText (the name of the first tab) (eg: "Third Party" for the Third Party element, "Product" for the Product element)

If no context is entered, changes made to the tab by the myfield will apply to all fields with the same label on all records.


Replacement text

text of your choice that will be displayed instead of the native label.

Author

the name of the creator of the myField

Display

  • Visible: the field will be displayed. This is the standard operation of Dolibarr.
  • Invisible: the field will be absent from the cards
  • Hidden: the field will be absent from the cards but can be displayed (Show/Hide).

Background Color

Use the color picker to determine the background color of the myField.

Move

Enter -1 to move the menu tab to the left, 1 to move the right.

Redirect URL

Enter the URL of the page that will be displayed when the menu tab is clicked. If this field is left blank, the native URL of the menu will be kept.


Indicate here only the part of the URL following /htdocs/

Display request: see Operation section, below

Following the creation of a myField, it will be necessary to define the access rights to the myFields by user groups from the secondary menu link of the same name (See section Configuring access rights).

Example of customizing a tab

Let's customize the tab sheet of the element sheets.

The sheet then becomes

If the tab is active, the color will be displayed on its edges

Fields

Creating myField

The myField creation page is accessible from the secondary menu link Patastools > MyField > New MyField.


myField Type

the field automatically filled in based on the menu link you clicked.

Native Label

enter here the native label of the field as it is displayed on the screen.

Activation Context

the activation context allows you to limit the action of myFields to only the fields of the pages with the context indicated here. If no context is entered, changes made to the tab by the myfield will apply to all fields with the same label on all records.

List of main contexts

Replacement text

text of your choice that will be displayed instead of the native label.

Author

the name of the creator of the myField

Display

  • Visible: the field will be displayed. This is the standard operation of Dolibarr.
  • Invisible: the field will be absent from the cards
  • Hidden: the field will be absent from the cards but can be displayed (Show/Hide).
on the latest versions of the module, (Show/Hide) is no longer used, you must now click on the Dolibarr version number (top right)

Background color

use the color selector to determine the background color of the myField.

Move

enter 1 to move up one field, -1 to move down one field.

Default value

Input field size

to be defined according to your needs. If left blank, the native value of the field is kept.

Mandatory:

check this box to make entering values ​​in the field mandatory to save the creation or modifications of the page

The control of the field in creation and modification is only carried out if you enter the edition of the field itself

Input mask

the input mask can be configured with the following characters:

  • a for a letter (A-Z,a-z)
  • 9 for a number (0-9)
  • for an alphanumeric character (A-Z,a-z,0-9)
You can add the characters you want to the field to make up your mask. For example, if you want to add an international code to the phone field, the mask will be: +0099-(9)999999999
  • UPPERCASE to force uppercase input.
  • LOWERCASE to force lowercase input.

Display request

See Operation section

Moving a field in a form is only done within its table. It is therefore possible to move a field up or down, but not to change its column

Following the creation of a field type myField, it will be necessary to define the access rights to the myFields by user groups from the secondary menu link of the same name (See section Configuring access rights).

Example of customizing a field

Let's customize the field Id. prof. 2 (SIRET) of third-party files.

The field has been set to invisible with a number input mask (999 999 999 99999)

By clicking on the Show/Hide link above the table, the field will be displayed according to the settings saved on the myField sheet


When editing the field, the mask will be activated and will only allow the predefined entry and its completion checked (made mandatory) to prevent the page from being saved without it being filled in.

Lists

It is possible to modify the fields of the native lists of dolibarr (the one with a field selection icon at the end of the list)


Creating myField

List myfields allow you to limit the display of fields. It is necessary to open the list page to retrieve information specific to this type of myField

  • the activation context
  • the untranslated label of the field

Example of setting

We will modify the "Third party" column on the list of interventions

Depending on the permissions, the field will also be inaccessible in the field selector.

If you make a list myField invisible, it will be invisible to all users. To hide it only from one or more groups of users, leave it visible and then add access rights!


Buttons

It is possible to modify the buttons present on the dolibarr files

Creation of myField

Button myfields allow you to make the button invisible, replace the label, the url associated with the button and make its access visible according to the result of an SQL query

With the native Dolibarr theme, the button label is capitalized, so you must use the original text that you retrieve with the right click and the inspect menu.

Conditional display SQL query

The processing query will condition the display of the fields according to the correspondence of the object to the query. It is then possible, for example, to display different fields depending on whether the object is a product or a service. It is possible to transmit two values ​​as parameters:

  • #ID#: the id of the main object of the page
  • #USERID#: the id of the active user

How it works

Enter here the display query applicable to the fields in the following example:

#SEL# allows you to replace the SELECT of the SQL query which will be blocked by Dolibarr's native security (SQL Injection)

#SEL# IF(fk_product_type=1, 1, 0) AS `read`, IF(fk_product_type=1, 1, 0) AS `write` FROM llx_product WHERE rowid=#ID#;

read allows you to authorize or not the global display of the field write allows you to authorize or not its modification (not necessary in the case of a button or a tab...)

If the value is 0, the field is hidden, otherwise it is displayed Be careful, if we leave the field parameter hidden, it will not appear regardless of the value

Example

With the following myfield

We obtain the following sheet on a product

While on the sheet of a service

Setting access rights to myFields, tabs and menus

Configuring access rights

As an administrator user, all myFields are visible to you.

On the MyField module home page, the application of customizations is disabled

If you have not defined any user groups, myfields are displayed on all users' interfaces.

From the secondary menu entry Patas-Tools > MyField > tab access rights, configure the accesses of the user groups:

There are four access rights:

Access blocked

Access read

Edit blocked

Edit access

Behavior according to access rights

Blocked in access ()

The field will be hidden from users in the group. They will not be able to view it

the Show/Hide link will not be active

Read access but blocked from editing ()

Users in the group will be able to view the field, but will not be able to edit its content.

Read access and Edit access ()

Users in the group will be able to view and edit the field if their group or user permissions allow them to do so. The field settings then apply (mandatory, input mask, etc.)

Other features

Importing myFields

It is possible to save a list of myfields and their settings by importing an XML file. From the Patas-M Tools > MyField > Import a tab page, paste the XML file into the input area and click on the Start import button.

If you check the Overwrite previous data box, your list of myfields will be limited to those present in the file you are importing

Then configure the users' access rights to the myField.

Activation context

A list of all available contexts is present on the dolibarr wiki: https://wiki.dolibarr.org/index.php?title=Hooks_System#List_of_Contexts_available_in_Dolibarr

some of the most common

Card Context
Member membertypecard
Categories categorycard
Orders ordercard
Supplier order ordersuppliercard
Contact contactcard
Contract contractcard
Donation doncard
Warehouse warehousecard
Shipping expeditioncard
Customer invoice invoicecard
Supplier invoice suppliercard


Sheet Context
Intervention interventioncard
Delivery deliverycard
Expense report tripandexpensecard
Product productcard
Project projectcard
Commercial proposal propalcard
Customer payment paymentcard
Supplier payment paymentsupplier
Salary salarycard
Task projecttaskcard
Third party thirdpartycard
User usercard

Frequently Asked Questions

General

This chapter lists the difficulties encountered with the module. You will therefore find answers to its use. If you encounter an error other than those described below when using this module:

  1. Disable and reactivate the module,
  2. Check on the ChangeLog if a new version has been published,
  3. Re-install/update the module,
  4. Check that replacing native Dolibarr files is not necessary for the module to work properly.
  5. Check that no incompatibility with another module is indicated. If necessary, follow our recommendations.

If, despite these manipulations, the error persists, contact us using the dedicated form (http://docs.patas-monkey.com/support/). This form is the preferred contact method for any difficulty of use or bug report. Also, we thank you for not multiplying the exchange channels for the same object.

Displaying a message at the top of Dolibarr pages

If your Dolibarr pages display a message similar to the following image, it is not an error message, but the display of the contexts of the current page. To no longer see these lines displayed, disable the display of the context (see Configuration).

Ordering error message

Some pages of some versions of Dolibarr have an error in their code preventing the correct application of field customization. MyField allows you to identify them in order to correct them.

The error message is displayed at the bottom of the page and is as follows:

Using the URL of the page, open the Dolibarr core file to edit it. For example, if the page containing the message is http://.../htdocs/custom/myField/admin/extrafields.php, successively open the folders htdocs, custom, myField, admin and open the file extrafields.php.

The error comes from the inversion of the lines llxFooter(); and $db->close(); at the end of the file.

Edit the page code to get

instead of

Multicompany

With the multicompany module, it is necessary to activate the module on each entity