CMS Made Simple Forums

Hi, not an issue, just a notice of compatibility LISE 1.3.1 ->LISE 1.4.x. If you edit an item after updating LISE you may sometimes get an error report such as "invalid item url" and you will not able to save the item. This error may be related to the new feature "Hide URL field from item editor". I...

And as this solution would also work with a detail view of a second instance, I can mark this topic as solved. Thanks again for helping me to help myself.

For other users who are also struggling a bit with Liseloader here is the solution a little more detailed. field definition in instance A of type: LISEInstanceItem. In my case it's not neccessary to use LISE Instance Item. Because I did not know about the help text in extensions->lise->module help->...

If you connect the items of instance A with items of instance B, you can get what you want. Like Jo Morg already wrote; using a field definition in instance A of type: LISEInstanceItem. I've been trying very to handle it. But - HOORAY - now got it. :D I was searching a long time for a help file for...

Thank you Jo and Velden, I'm not sure I understand why you would want to use the url for this. Currenty it is no longer needed to get to detailpage of instance B. But it is still not finished. I try to explain what this is all about. Instance A is the home page. An image gallery. All images are reff...

Hi, as described in the title: I'm wondering, if it may be possible to connect a single item of instance A with a detail view of instance B by using the $item->url tag, not by inserting the generated url manually. For example (simplified summary template of instance A): {foreach from=$items item=ite...

I do not think that this is a LISE issue. I guess it's anything about a responsive design breakpoint. I recognise exactly the same behaviour when the browser-width is too small. For example when I have my bookmarks or chronic opened on the left side of the browser. I'm using a 19" display. The icons...

Jo Morg wrote: ↑Sun Oct 11, 2020 4:32 pm New version released, I think it's properly fixed now. thanks!

YES!! Importing and duplicating instances works fine now. Thank you!

if it was deleted it was by the OP I guess that too. Maybe because he published some private data in his error report (directories not anonymized). Or maybe he could fix ist. It was the same report as in my first post when trying to duplicate instances. Fatal error: Uncaught ## 00002: LISE Database...

antibart wrote: ↑Tue Oct 06, 2020 7:24 am Seems that I'm the only one

Sorry. NOT the only one. No matter: the bug report has been deleted from the forge anyway.

Seems that I'm the only one who gets this error. Another user reportet the same issue in the bug tracker for LISE 1.4.1.

What error exactly are you getting? Also, what version of PHP are you running? I have tested this exhaustively before and after releasing 1.4.1 and haven't been able to reproduce any further errors. Meanwhile I am back to LISE 1.3.1 an cannot check again. According to the release notes I've checked...

Remove the instances you have created since upgrading ... I cannot duplicate or import any instances since upgrading. That is the problem.:( It is exactly the way you say it: After importing the files are created, but no instance is available. So goto Module Manager and remove the LISE Instances wh...

kierweb wrote: ↑Fri Oct 02, 2020 10:12 am before trying to import them again!

I didn't try to import existing instances. I had two existing instances before the update and they work fine. The errors appear when trying to import another instance from vs. 1.3.1 or duplicate a new instance.

Jo Morg wrote: ↑Thu Oct 01, 2020 4:38 pm New version released: 1.4.1.

Thanks Jo,

but updating to 1.4.1 didn't fix the errors

Existing instance will be updated fine - but new instances or importing causes the same errors and white pages as before.