ANNOUNCEMENT: CustomFields v3 and ProductsEasyAccess are now free and opensource!
You can now download the latest version of CustomFields and ProductsEasyAccess here:
CustomFields and ProductsEasyAccess are now completely opensourced. This was a great adventure, and I want to thank everyone who supported and contributed to the project, which allowed me to continue to develop and add significant new features over the past years.
Nevertheless, it is now time for me to move on to other projects. Thus, I publish these modules under opensource, as was planned from the beginning. I hope that the module will continue to live with the user community, the module being stable enough to continue to work with all future versions of Dolibarr as long as Hooks and Triggers systems do not change.
I therefore will not provide personalized support anymore, but the github is open to all contributors and I will pull for any stable contribution.
I hope this module will continue to provide a tailored user experience to the community of Dolibarr! Enjoy!
I have a fresh installed Dolibarr 3.8.3 on FreeBSD 9.3 with Postgresql and PHP 5.6.16. Also I installed CustomFields 3.5.13. The configuration looks ok, I can access to the setup page of CustomFields, but when I try to start initialize with <Create Table> I got the following messages:
ERROR: 42703: column ‘column_key’ does not exist LINE 3: …A = ‘dolibarr’ AND TABLE_NAME = ‘llx_facture’ AND COLUMN_KEY… ^ LOCATION: errorMissingColumn, parse_relation.c:2655
ERROR: 42703: column ‘column_key’ does not exist LINE 3: …A = ‘dolibarr’ AND TABLE_NAME = ‘llx_facture’ AND COLUMN_KEY… ^ LOCATION: errorMissingColumn, parse_relation.c:2655; ERROR: 42601: syntax error at end of input LINE 1: … llx_facture_customfields( rowid SERIAL PRIMARY KEY ^ LOCATION: scanner_yyerror, scan.l:1045
ERROR: 42703: column ‘column_key’ does not exist LINE 3: …A = ‘dolibarr’ AND TABLE_NAME = ‘llx_facture’ AND COLUMN_KEY… ^ LOCATION: errorMissingColumn, parse_relation.c:2655; ERROR: 42601: syntax error at end of input LINE 1: … llx_facture_customfields( rowid SERIAL PRIMARY KEY ^ LOCATION: scanner_yyerror, scan.l:1045
no, I did not, because I 've read that the author wants only to communicate via the forum and not e-mail.
Ok, I changed the database from postgresql to mysql. Now the modul CustomFields runs like it is expected. Well, other users with postgresql back end watch out, it will not working with this modul.
I cannot get the ODT fields to show replacement value.
The PDF test seems to be working.
In the CustomFields Setup, on the “Customer Invoices” tab, I have a variable name “cf_bankinfo”.
The PDF test from the “Invoice card” screen shows:
bankinfo ($object->customfields->cf_bankinfo): test
bankinfo [raw] ($object->customfields->raw->cf_bankinfo): test
In my customized ODT file I have entered:
{cf_bankinfo}
and all other variables show appropriate values except this one which still shows:
{cf_bankinfo}
instead of the repalcement txt “test”
@Antknee Please make sure your tag was not corrupted with ODT markup (for example when you use backspace to correct your writing, it may insert hidden ODT markup, breaking the tag).
What you can do to ensure that your tag is not broken is to write it down in a simple text editor such as Notepad (or Notepad++ or SublimeText, etc.) and then copy/paste this tag into your ODT document. This should fix your issue.
Hello,
I get the following errors when I access any module setup page and then go to custom fields:
Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation ‘=’
Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation ‘=’
I am using Dolibarr 5.6
Custom fields version 3.6.0
Please help
I got the same issues when trying to use the module with a 6.0.3 Dolibarr I freshly installed. I had to completely reinstall, as I found out that some errors were still triggered even after deleting all the module files: for example I was unable to clone products.
Did you find a solution to the issue?