-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Develop #2
Closed
Closed
Develop #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pourquoi tu m’envoies ce pull ? |
C'est un test pr valider la synchro des autres repo. A+ Herve Prot Le 28 août 2011 à 19:02, hregis reply@reply.github.com a écrit :
|
eldy
pushed a commit
that referenced
this pull request
Aug 9, 2012
marcosgdf
pushed a commit
to marcosgdf/dolibarr
that referenced
this pull request
Feb 19, 2015
abcnet-lu
pushed a commit
to abcnet-lu/dolibarr
that referenced
this pull request
Feb 19, 2016
Merge back official Dolibarr develop into my abcnet-lu fork
atm-florian
pushed a commit
to atm-florian/dolibarr
that referenced
this pull request
Nov 7, 2016
New fonctionnalité RTT avec les congés payés de Dolibarr
eldy
pushed a commit
that referenced
this pull request
Jan 15, 2017
Fix: Add Missing Translation String
eldy
pushed a commit
that referenced
this pull request
Jun 13, 2018
eldy
pushed a commit
that referenced
this pull request
Jun 18, 2018
eldy
pushed a commit
that referenced
this pull request
Feb 26, 2024
Default value of the parameter #2 $mesgarray (string) of function get_htmloutput_mesg() is incompatible with type array<string>.
Merged
atm-thomasb
pushed a commit
to atm-thomasb/dolibarr
that referenced
this pull request
Sep 19, 2024
Fix 1.0 divers
cfoellmann
added a commit
to cfoellmann/dolibarr
that referenced
this pull request
Sep 19, 2024
thersane-john
pushed a commit
to thersane-john/dolibarr
that referenced
this pull request
Oct 25, 2024
…entMessage New documentation ux set event message
alexandre-janniaux
added a commit
to alexandre-janniaux/dolibarr
that referenced
this pull request
Jan 8, 2025
`WHERE xx IN ()` is not allowed in PostgreSQL queries, and result in the following fatal error: GROUP BY fk_facture_fourn 33 DoliDBPgsql::query SQL Error message: ERROR: 42601: syntax error at or near ")" LINE 10: AND fk_facture_fourn IN () ^ We can check whether we have valid invoices before running the query, since the query will only check whether the invoices are complete or not. It also fixes the following error on the development PHP output. Fatal error: Uncaught TypeError: pg_num_rows(): Argument Dolibarr#1 ($result) must be of type PgSql\Result, bool given in /var/www/html/core/db/pgsql.class.php:654 Stack trace: #0 /var/www/html/core/db/pgsql.class.php(654): pg_num_rows(false) Dolibarr#1 /var/www/html/accountancy/journal/purchasesjournal.php(418): DoliDBPgsql->num_rows(false) Dolibarr#2 {main} thrown in /var/www/html/core/db/pgsql.class.php on line 654
alexandre-janniaux
added a commit
to alexandre-janniaux/dolibarr
that referenced
this pull request
Jan 8, 2025
`WHERE xx IN ()` is not allowed in PostgreSQL queries, and result in fatal errors. We can check whether we have valid invoices before running the query, since the query will only check whether the invoices are complete or not. It also fixes the following error on the development PHP output: Fatal error: Uncaught TypeError: pg_num_rows(): Argument Dolibarr#1 ($result) must be of type PgSql\Result, bool given in /var/www/html/core/db/pgsql.class.php:654 Stack trace: #0 /var/www/html/core/db/pgsql.class.php(654): pg_num_rows(false) Dolibarr#1 /var/www/html/accountancy/journal/expensereportsjournal.php(264): DoliDBPgsql->num_rows(false) Dolibarr#2 {main} thrown in /var/www/html/core/db/pgsql.class.php on line 654
alexandre-janniaux
added a commit
to alexandre-janniaux/dolibarr
that referenced
this pull request
Jan 8, 2025
`WHERE xx IN ()` is not allowed in PostgreSQL queries, and result in the following fatal error: GROUP BY fk_facture_fourn 33 DoliDBPgsql::query SQL Error message: ERROR: 42601: syntax error at or near ")" LINE 10: AND fk_facture_fourn IN () ^ We can check whether we have valid invoices before running the query, since the query will only check whether the invoices are complete or not. It also fixes the following error on the development PHP output. Fatal error: Uncaught TypeError: pg_num_rows(): Argument Dolibarr#1 ($result) must be of type PgSql\Result, bool given in /var/www/html/core/db/pgsql.class.php:654 Stack trace: #0 /var/www/html/core/db/pgsql.class.php(654): pg_num_rows(false) Dolibarr#1 /var/www/html/accountancy/journal/purchasesjournal.php(418): DoliDBPgsql->num_rows(false) Dolibarr#2 {main} thrown in /var/www/html/core/db/pgsql.class.php on line 654 Fixes Dolibarr#32374
alexandre-janniaux
added a commit
to alexandre-janniaux/dolibarr
that referenced
this pull request
Jan 8, 2025
`WHERE xx IN ()` is not allowed in PostgreSQL queries, and result in fatal errors. We can check whether we have valid invoices before running the query, since the query will only check whether the invoices are complete or not. It also fixes the following error on the development PHP output: Fatal error: Uncaught TypeError: pg_num_rows(): Argument Dolibarr#1 ($result) must be of type PgSql\Result, bool given in /var/www/html/core/db/pgsql.class.php:654 Stack trace: #0 /var/www/html/core/db/pgsql.class.php(654): pg_num_rows(false) Dolibarr#1 /var/www/html/accountancy/journal/expensereportsjournal.php(264): DoliDBPgsql->num_rows(false) Dolibarr#2 {main} thrown in /var/www/html/core/db/pgsql.class.php on line 654 Refs Dolibarr#32374 but for the expensereportsjournal page.
eldy
pushed a commit
that referenced
this pull request
Jan 9, 2025
`WHERE xx IN ()` is not allowed in PostgreSQL queries, and result in the following fatal error: GROUP BY fk_facture_fourn 33 DoliDBPgsql::query SQL Error message: ERROR: 42601: syntax error at or near ")" LINE 10: AND fk_facture_fourn IN () ^ We can check whether we have valid invoices before running the query, since the query will only check whether the invoices are complete or not. It also fixes the following error on the development PHP output. Fatal error: Uncaught TypeError: pg_num_rows(): Argument #1 ($result) must be of type PgSql\Result, bool given in /var/www/html/core/db/pgsql.class.php:654 Stack trace: #0 /var/www/html/core/db/pgsql.class.php(654): pg_num_rows(false) #1 /var/www/html/accountancy/journal/purchasesjournal.php(418): DoliDBPgsql->num_rows(false) #2 {main} thrown in /var/www/html/core/db/pgsql.class.php on line 654 Fixes #32374
eldy
pushed a commit
that referenced
this pull request
Jan 9, 2025
`WHERE xx IN ()` is not allowed in PostgreSQL queries, and result in fatal errors. We can check whether we have valid invoices before running the query, since the query will only check whether the invoices are complete or not. It also fixes the following error on the development PHP output: Fatal error: Uncaught TypeError: pg_num_rows(): Argument #1 ($result) must be of type PgSql\Result, bool given in /var/www/html/core/db/pgsql.class.php:654 Stack trace: #0 /var/www/html/core/db/pgsql.class.php(654): pg_num_rows(false) #1 /var/www/html/accountancy/journal/expensereportsjournal.php(264): DoliDBPgsql->num_rows(false) #2 {main} thrown in /var/www/html/core/db/pgsql.class.php on line 654 Refs #32374 but for the expensereportsjournal page.
eldy
pushed a commit
that referenced
this pull request
Jan 9, 2025
`WHERE xx IN ()` is not allowed in PostgreSQL queries, and result in the following fatal error: GROUP BY fk_facture_fourn 33 DoliDBPgsql::query SQL Error message: ERROR: 42601: syntax error at or near ")" LINE 10: AND fk_facture_fourn IN () ^ We can check whether we have valid invoices before running the query, since the query will only check whether the invoices are complete or not. It also fixes the following error on the development PHP output. Fatal error: Uncaught TypeError: pg_num_rows(): Argument #1 ($result) must be of type PgSql\Result, bool given in /var/www/html/core/db/pgsql.class.php:654 Stack trace: #0 /var/www/html/core/db/pgsql.class.php(654): pg_num_rows(false) #1 /var/www/html/accountancy/journal/purchasesjournal.php(418): DoliDBPgsql->num_rows(false) #2 {main} thrown in /var/www/html/core/db/pgsql.class.php on line 654 Fixes #32374
eldy
pushed a commit
that referenced
this pull request
Jan 9, 2025
`WHERE xx IN ()` is not allowed in PostgreSQL queries, and result in fatal errors. We can check whether we have valid invoices before running the query, since the query will only check whether the invoices are complete or not. It also fixes the following error on the development PHP output: Fatal error: Uncaught TypeError: pg_num_rows(): Argument #1 ($result) must be of type PgSql\Result, bool given in /var/www/html/core/db/pgsql.class.php:654 Stack trace: #0 /var/www/html/core/db/pgsql.class.php(654): pg_num_rows(false) #1 /var/www/html/accountancy/journal/expensereportsjournal.php(264): DoliDBPgsql->num_rows(false) #2 {main} thrown in /var/www/html/core/db/pgsql.class.php on line 654 Refs #32374 but for the expensereportsjournal page.
eldy
pushed a commit
that referenced
this pull request
Jan 9, 2025
`WHERE xx IN ()` is not allowed in PostgreSQL queries, and result in the following fatal error: GROUP BY fk_facture_fourn 33 DoliDBPgsql::query SQL Error message: ERROR: 42601: syntax error at or near ")" LINE 10: AND fk_facture_fourn IN () ^ We can check whether we have valid invoices before running the query, since the query will only check whether the invoices are complete or not. It also fixes the following error on the development PHP output. Fatal error: Uncaught TypeError: pg_num_rows(): Argument #1 ($result) must be of type PgSql\Result, bool given in /var/www/html/core/db/pgsql.class.php:654 Stack trace: #0 /var/www/html/core/db/pgsql.class.php(654): pg_num_rows(false) #1 /var/www/html/accountancy/journal/purchasesjournal.php(418): DoliDBPgsql->num_rows(false) #2 {main} thrown in /var/www/html/core/db/pgsql.class.php on line 654 Fixes #32374
eldy
pushed a commit
that referenced
this pull request
Jan 9, 2025
`WHERE xx IN ()` is not allowed in PostgreSQL queries, and result in fatal errors. We can check whether we have valid invoices before running the query, since the query will only check whether the invoices are complete or not. It also fixes the following error on the development PHP output: Fatal error: Uncaught TypeError: pg_num_rows(): Argument #1 ($result) must be of type PgSql\Result, bool given in /var/www/html/core/db/pgsql.class.php:654 Stack trace: #0 /var/www/html/core/db/pgsql.class.php(654): pg_num_rows(false) #1 /var/www/html/accountancy/journal/expensereportsjournal.php(264): DoliDBPgsql->num_rows(false) #2 {main} thrown in /var/www/html/core/db/pgsql.class.php on line 654 Refs #32374 but for the expensereportsjournal page.
alexandre-janniaux
added a commit
to alexandre-janniaux/dolibarr
that referenced
this pull request
Jan 21, 2025
Fix the following error: Fatal error: Uncaught TypeError: pg_num_rows(): Argument Dolibarr#1 ($result) must be of type PgSql\Result, bool given in /var/www/html/core/db/pgsql.class.php:654 Stack trace: #0 /var/www/html/core/db/pgsql.class.php(654): pg_num_rows(false) Dolibarr#1 /var/www/html/accountancy/journal/expensereportsjournal.php(264): DoliDBPgsql->num_rows(false) Dolibarr#2 {main} thrown in /var/www/html/core/db/pgsql.class.php on line 654
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For testing pull request.
Only delete old id present in files after the last synchro from cvs