Skip to content
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
wants to merge 2 commits into from
Closed

Develop #2

wants to merge 2 commits into from

Conversation

ghost
Copy link

@ghost ghost commented Aug 28, 2011

For testing pull request.
Only delete old id present in files after the last synchro from cvs

@hregis
Copy link
Contributor

hregis commented Aug 28, 2011

pourquoi tu m’envoies ce pull ?

@hregis hregis closed this Aug 28, 2011
@ghost
Copy link
Author

ghost commented Aug 28, 2011

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 :

pourquoi tu m’envoies ce pull ?

Reply to this email directly or view it on GitHub:
#2 (comment)

eldy pushed a commit that referenced this pull request Aug 9, 2012
eldy added a commit that referenced this pull request Jul 21, 2014
eldy pushed a commit that referenced this pull request Nov 4, 2014
marcosgdf pushed a commit to marcosgdf/dolibarr that referenced this pull request Feb 19, 2015
FHenry referenced this pull request in FHenry/dolibarr Aug 12, 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 May 10, 2018
dolibarr up to date fork
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 Jul 15, 2018
eldy pushed a commit that referenced this pull request Aug 29, 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>.
@frederic34 frederic34 mentioned this pull request Apr 22, 2024
atm-thomasb pushed a commit to atm-thomasb/dolibarr that referenced this pull request Sep 19, 2024
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
eldy pushed a commit that referenced this pull request Nov 8, 2024
eldy pushed a commit that referenced this pull request Jan 5, 2025
…picious order for arguments named tooltip and name - These are being passed to parameters #2 (string htmltext) and #8 (string tooltiptrigger)
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant