LISE 1.5.4 some notes
Posted: Sat May 20, 2023 1:15 pm
Hi,
it's not that important, maybe just misunderstandings. Just some things I noticed working with LISE 1.5.4. last weeks.
1. I have an instance with "Hide alias field.." and "Hide URL field" NOT enabled.
When I clone the instance these two fields are enabled by default. Copying the instance-tag into a template or editor crashes the frontend page. "Crashing" means: the html source code begins with the body tag and ends at the place the LISE content should be displayed.
Subsequent deactivation of the two fields solves the problem.
2. When csv-importing items into an instance the import starts correctly with a message such as "Stage one finished. Stage two has started" or similar.
Below this message is a status report "280 entries imported, time left 00:00:05, estimated time 00:00:10 ...". This status report is not completed and continues to run endless. It's still running after two hours. So there is no other choice but to cancel. Nevertheless, all entries are correctly imported.
Although the import works fine, it's a bit misleading when you're expecting a completion message.
...
it's not that important, maybe just misunderstandings. Just some things I noticed working with LISE 1.5.4. last weeks.
1. I have an instance with "Hide alias field.." and "Hide URL field" NOT enabled.
When I clone the instance these two fields are enabled by default. Copying the instance-tag into a template or editor crashes the frontend page. "Crashing" means: the html source code begins with the body tag and ends at the place the LISE content should be displayed.
Subsequent deactivation of the two fields solves the problem.
2. When csv-importing items into an instance the import starts correctly with a message such as "Stage one finished. Stage two has started" or similar.
Below this message is a status report "280 entries imported, time left 00:00:05, estimated time 00:00:10 ...". This status report is not completed and continues to run endless. It's still running after two hours. So there is no other choice but to cancel. Nevertheless, all entries are correctly imported.
Although the import works fine, it's a bit misleading when you're expecting a completion message.
...