Open asirota opened 3 months ago
Attached is an example of a Page Export.
A page export would create a CSV of not only the existing modifications on the page, but of every EZ-editable (directly contains text) element, along with it's EZ Tag, custom label, and optionally it's original text content. This would allow bulk editing, and if more modifications are needed per element, simply duplicate the line as shown in the attached CSV. The modificationId
column would be left empty when creating new entries.
EZ-Designer - EZ Wild Apricot Web Designer Demo - Membership (1717068763800).csv
Would this work for our needs?
Can you make the file have the replacement text column next to the original text column? that way it will be easier to compare them side by side and make it easier to do translation fill out.
I see you're also putting all the languages in one file as well as the global changes. Can you sort by the language field so they are all grouped together when exported?
Here's how I modified the column order
EZ-Designer.-.EZ.Wild.Apricot.Web.Designer.Demo.-.Membership.1717068763800.csv
I also noted that the modType column was in there twice? I think that's a bug
I see you're also putting all the languages in one file as well as the global changes. Can you sort by the language field so they are all grouped together when exported?
I can, but wouldn't having the same elements grouped together be better? Also, you can then re-sort as needed in Excel. Currently, the elements are listed in the order they appear on the website.
Here's how I modified the column order
I'm working on the order, I may simplify the csv more.
I also noted that the modType column was in there twice? I think that's a bug
That's just in this file.
Ah I didn't know they are in the order as on the website. Well let's just see how it goes. I assume when you go to another page and download the file it takes all the existing edits and adds the ones on the current page that is available to edit?
On each page, only the elements on that page will be exported, along with modifications with matching EZ tags. So if there is an element that is only on the home page, will will not be included on the about page export. There will be an option to export the whole json file, but it will not include unedited elements like the page exports do
in the EZ3 UI have a way to download all the keys/values of targeted elements in a XLSX/CSV file so that they can be edited in bulk and uploaded back into the system
The export should have the EZTag as part of the export.
The upload of the file should be then converted back into the JSON format.