Changes

m
Line 1: Line 1:  +
<!-- BEGIN origin interlang links -->
 +
<!-- You can edit this section but do NOT remove these comments
 +
    Links below will be automatically replicated on translated pages by PolyglotBot -->
 +
[[fr:Troubleshooting_FR]]
 +
[[es:Troubleshooting_ES]]
 +
[[zh:故障排除]]
 +
<!-- END interlang links -->
 +
 
[[Category:FAQ_EN]]
 
[[Category:FAQ_EN]]
 
This page will list all the common technical problems you can run into.
 
This page will list all the common technical problems you can run into.
   −
If you run into a problem, the first step is to activate the Syslog module, then to redo the steps that leads you to a bug, and then check the log file residing at '''/documents/dolibarr.log'''
      
= Dolibarr ask my login or password each time I click on a new link =
 
= Dolibarr ask my login or password each time I click on a new link =
Line 22: Line 29:  
* A wrong permission for the /documents/ folder, so that Dolibarr can't rename the folder. If that's the case, you should have in your syslog something like:
 
* A wrong permission for the /documents/ folder, so that Dolibarr can't rename the folder. If that's the case, you should have in your syslog something like:
   −
<source lang=text>
+
<syntaxHighlight lang=text>
 
ERROR 127.0.0.1 user fiche Interfaces::run_triggers action=ORDER_SUPPLIER_VALIDATE Files found: 6, Files launched: 5, Done: 0, Failed: 1
 
ERROR 127.0.0.1 user fiche Interfaces::run_triggers action=ORDER_SUPPLIER_VALIDATE Files found: 6, Files launched: 5, Done: 0, Failed: 1
 
ERROR 127.0.0.1 user fiche CommandeFournisseur::valid  
 
ERROR 127.0.0.1 user fiche CommandeFournisseur::valid  
 
DEBUG 127.0.0.1 user fiche ROLLBACK Transaction
 
DEBUG 127.0.0.1 user fiche ROLLBACK Transaction
</source>
+
</syntaxHighlight>
    
* A wrong custom numerotation system: if you use illegal characters for the filesystem (like "/"), this will crash whenever you'll try to validate your document since it won't be able to use this illegal character in the renaming. Try to disable your current custom numerotation system and enable the default one temporarily to see if this fixes the issue.
 
* A wrong custom numerotation system: if you use illegal characters for the filesystem (like "/"), this will crash whenever you'll try to validate your document since it won't be able to use this illegal character in the renaming. Try to disable your current custom numerotation system and enable the default one temporarily to see if this fixes the issue.
Line 34: Line 41:     
What repair can do :
 
What repair can do :
* Run repair SQL file
+
* Run repair SQL file.
 
* Search list of fields declared and list of fields created into databases, then create fields missing
 
* Search list of fields declared and list of fields created into databases, then create fields missing
 
* Clean data into ecm_directories table
 
* Clean data into ecm_directories table
* Move logos to correct new directory.
+
* Move logos to correct new directory
 
* Rebuild thumbs for product files
 
* Rebuild thumbs for product files
 
* Check and clean linked elements
 
* Check and clean linked elements
Line 44: Line 51:  
* Check and clean linked elements
 
* Check and clean linked elements
 
* Clean data into const when files of module were removed without being
 
* Clean data into const when files of module were removed without being
 +
 +
To operate, the page should be opened with at least one command:
 +
* /install/repair.php?standard=confirmed
 +
* /install/repair.php?clean_linked_elements=confirmed
 +
* /install/repair.php?restore_thirdparties_logos=confirmed
 +
* /install/repair.php?clean_menus=confirmed
 +
* /install/repair.php?clean_orphelin_dir=confirmed
 +
* /install/repair.php?clean_product_stock_batch=confirmed
 +
* /install/repair.php?set_empty_time_spent_amount=confirmed
 +
* /install/repair.php?rebuild_product_thumbs=confirmed
 +
* /install/repair.php?force_disable_of_modules_not_found=confirmed
 +
* /install/repair.php?clean_perm_table=confirmed
 +
* /install/repair.php?force_utf8_on_tables=confirmed for Mysql only, when ''Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '=' ''
 +
 +
= I can't upload files  =
 +
 +
<span style="color: #FF0000;">This section needs more informations.</span>
 +
 +
Depending of your configuration, if you encounter the error
 +
<syntaxHighlight lang="php">
 +
Warning: tempnam(): open_basedir restriction in effect. File(C:\WINDOWS\TEMP) is not within the allowed path(s): (c:/dolibarr) in C:\dolibarr\www\dolibarr\htdocs\core\modules\import\import_xlsx.modules.php on line 182
 +
</syntaxHighlight>
 +
 +
You will have to edit the php.ini
 +
Find the directive upload_tmp_dir: uncomment the line and change its value to a required path. In this example it is "/var/tmp":
 +
 +
<syntaxHighlight lang="php">
 +
; Temporary directory for HTTP uploaded files (will use system default if not
 +
; specified).
 +
; http://php.net/upload-tmp-dir
 +
upload_tmp_dir = /var/tmp
 +
</syntaxHighlight>
 +
Additionally for PHP versions 5.5 and greater, find the directive sys_temp_dir: uncomment the line and change its value to a required path. In this example, it is "/var/tmp":
 +
<syntaxHighlight lang="php">
 +
; Directory where the temporary files should be placed.
 +
; Defaults to the system default (see sys_get_temp_dir)
 +
sys_temp_dir = "/var/tmp"
 +
</syntaxHighlight>
 +
 +
And in Vhosts
 +
<syntaxHighlight lang="c">
 +
open_basedir = {WEBSPACEROOT}{/}{:}{TMP}{/}:/var/tmp
 +
</syntaxHighlight>
    
= My problem is not in the list =
 
= My problem is not in the list =
 +
==Getting debug information==
 +
Dolibarr has a system to record logs of what it does and which errors occur. If you run into a problem, the first step is to activate the [[Error reporting|Log Debug]] module, then redo the steps that leads you to a bug, and then check the log file residing at '''/documents/dolibarr.log'''
 +
 +
Your web server has also error logging feature. See [[Error reporting|Log Debug]].
   −
If the solution for your problem couldn't be found in this page, please keep in a safe place a maximum of detailed informations (like the dolibarr log, php version, database type and version, dolibarr's version, Apache's log...), and seek help at the following organisms:
+
==Help and support==
 +
If the solution for your problem couldn't be found with tools in this page, please keep in a safe place a maximum of detailed informations (like the dolibarr log, php version, database type and version, dolibarr's version, Apache's log...), and seek help using one of those channels:
    
http://wiki.dolibarr.org/index.php/Dolibarr_help_and_support
 
http://wiki.dolibarr.org/index.php/Dolibarr_help_and_support