Hello, I have a problem with the report, only a few records, the word file does not open with error: error xml parsing, in addition, some fields in other reports, which contain special characters, e.g. T & T is reported as T & amp; T (obviously without spaces). What can I do? Thanks in advance
update: the xml error problem is still due to special characters. If there is an accented letter in the field, the xml error appears and the word file does not open. The table is utf8 GeneralCi collation and has no problem in any other display
Hi Miljko, I try this solution, if everything works out I will be happy. But I think I will have to ask for your intervention in the system because I also have big problems with wpdatatables plugin. Your colleague must have the credentials to fix (I hope) all things.
I have a wpdatatable table showing only the user data logged in, enabling check "Limit editing to user's own data only".
when I download the report quando io scarico il report con Report Builder, the zip file contains all the data of the entire table unfiltered. Obviously I activated the ceck "Follow filtering table" but that does not seem to work.
I believe that "Limit editing to user's own data only" on wpdatatable, is not recognized as a filter by Report Builder.
I added this to our to do list and this will be included in one of the future version of the plugin. We planed to release next version with already solved bugs real soon so I cannot promise that it will be included in that one but we will include it in one after that
Hello, I have a problem with the report, only a few records, the word file does not open with error: error xml parsing, in addition, some fields in other reports, which contain special characters, e.g. T & T is reported as T & amp; T (obviously without spaces). What can I do? Thanks in advance
update: the xml error problem is still due to special characters. If there is an accented letter in the field, the xml error appears and the word file does not open. The table is utf8 GeneralCi collation and has no problem in any other display
Hi Axelmet,
Please send me your temporary admin credentials so I can take a look. You have option to reply privately
Hi Axelmet,
You need to replace couple of files which you can find in the attachemnt
../wp-content/plugins/reportbuilder/assets/js/admin/reports_browse.js
../wp-content/plugins/reportbuilder/lib/PHPWord/TemplateProcessor.php
../wp-content/plugins/reportbuilder/source/class.abstract.builder.php
Please let me know does it helps
Hi Miljko,
I try this solution, if everything works out I will be happy.
But I think I will have to ask for your intervention in the system because I also have big problems with wpdatatables plugin. Your colleague must have the credentials to fix (I hope) all things.
I persuaded my clients of your seriousness
I'll let you know how the changes have gone.
For now, thank you.
a.
Hi Miljko,
Everything works, I replaced the files but I believe we need minify them.
it's possible? how?
Hi Axelmet,
You do not need to minify files. We will include this fixes along others in new version which we will release soon
UPDATE:
workaround: I changed the query giving up filter, now works
______________________________________________________________________
Another problem:
I have a wpdatatable table showing only the user data logged in, enabling check "Limit editing to user's own data only".
when I download the report quando io scarico il report con Report Builder, the zip file contains all the data of the entire table unfiltered.
Obviously I activated the ceck "Follow filtering table" but that does not seem to work.
I believe that "Limit editing to user's own data only" on wpdatatable, is not recognized as a filter by Report Builder.
How can I do?
thank you
There are still problems with special characters.
If a field contains an "&" the report goes back into error "xml parsing."
Hi Axelmet,
"&" sign is illegal in XML and we are working on solution for this. In meantime please use HTML ENTITY instead of ampersand and it should work
Ok, I have realized, I patiently wait for the correction :)
You can just tell me if it is provided for in a next update?
a.
Hi Axelmet,
I added this to our to do list and this will be included in one of the future version of the plugin. We planed to release next version with already solved bugs real soon so I cannot promise that it will be included in that one but we will include it in one after that