Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC:

Default layout replaced by modal 04 Jun 2017 22:09 #15181

  • Ferm
  • Ferm's Avatar Topic Author
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 39
  • Thank you received: 6
Something strange started happening this evening. For list views, when I want to add a menu item to show the default layout for a view, the menu item will have &layout=modal added to it and will therefore not work. If I puot in the url in the address bar manually without the layout=modal, it works fine. The problem is how to get a menu item that actually points to it.

If I have several list layouts with different names, the ones that are not default are fine and the menu item url will include the correct &layout=. However, the default layout will not work and will be &view=modal. This seems to be true whether the default layout is actually called default or something else.

This started only today and it seems to be the same for the legacy versions as well.

Please Log in or Create an account to join the conversation.

Last edit: by Ferm.

Default layout replaced by modal 05 Jun 2017 12:45 #15183

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
Because I am working on that (Modal pickers in forms). I didn't expected this change.
Checking...
Coding is now a piece of cake

Please Log in or Create an account to join the conversation.

Default layout replaced by modal 05 Jun 2017 13:05 #15184

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
Which release version are you using ?
Coding is now a piece of cake

Please Log in or Create an account to join the conversation.

Default layout replaced by modal 06 Jun 2017 21:32 #15194

  • Ferm
  • Ferm's Avatar Topic Author
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 39
  • Thank you received: 6
I tried 3.1.1, 3.15 and also the legacy version and I got the same result with all of them. I don't think I tried the beta version.

Please Log in or Create an account to join the conversation.

Last edit: by Ferm.

Default layout replaced by modal 09 Jun 2017 12:44 #15199

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
Do you have a FRONT LIST LAYOUT defined ?

Which PTL ?
Coding is now a piece of cake

Please Log in or Create an account to join the conversation.

Default layout replaced by modal 09 Jun 2017 15:33 #15202

  • Ferm
  • Ferm's Avatar Topic Author
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 39
  • Thank you received: 6
I am not sure I understand your question. There is a front list layout defined, yes. The problem is when I try to add a menu item pointing to it. The url then includes &layout=modal which seems to cause the problem. This is only the case for the default layout. If I have more than one list layout defined, it will work for the one which is not the default as the url will include &layout=name where name is the name of the non-default layout. The problem is the same with all tables.

What do you mean by PTL?

Please Log in or Create an account to join the conversation.

Default layout replaced by modal 09 Jun 2017 16:18 #15203

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
PTL = Project / Table / Layout

I asked you this because the builder is searching for the first layout defined and if you don't have front list layout (LIST), then it is possible that the modal layout is used, but that's strange.
It was just a question for finding the bug.
Coding is now a piece of cake

Please Log in or Create an account to join the conversation.

Default layout replaced by modal 06 Jul 2017 21:16 #15240

I am also experiencing the same problem.

Please Log in or Create an account to join the conversation.

Default layout replaced by modal 06 Jul 2017 21:55 #15241

After spending four hours on this assuming that I was doing something wrong and that it was not the UI… The issue is the UI. What I discovered was that if you the star on the page layout it messes up the "default" function. It will automatically make the call to modal rather than to default. The way I worked this out was that I created additional layouts then deleted the layout that was starred. There is no way to toggle the star on and off. Once the star is selected your stuck. This only seems to be the case on the front and collection layouts. Clearly this is a bug. I was super appreciate if this can be fixed in the next 48 hours as I have several dozen components to create. I been using this tool for several years now and this is the first time I've seen something this bad appear in this otherwise hugely timesaving tool.

Please Log in or Create an account to join the conversation.

Default layout replaced by modal 06 Jul 2017 22:14 #15242

  • Ferm
  • Ferm's Avatar Topic Author
  • Offline
  • Junior Member
  • Junior Member
  • Posts: 39
  • Thank you received: 6
To work around this problem, you can just edit the #__menu table in your database. Once you have created the menu option, the url will be in the link field of the #__menu table. Just edit that field for the menu entry you jsut created and take out the layout=modal bit from the url. This is what I did to get around it.

Please Log in or Create an account to join the conversation.

Default layout replaced by modal 07 Jul 2017 10:22 #15243

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
Fixed.
It should be better now.

For info, the XML layout file 'modal.xml' was causing trouble.
It is useless and create this problem.
I think it started to appear after I modified a core function of Cook.
That's all in place now.

For users with expired account, manual fix is following :
-> delete all files named 'modal.xml'
They should all be located in
FRONT/views/xxx/tmpl/
Coding is now a piece of cake

Please Log in or Create an account to join the conversation.

Last edit: by admin.
  • Page:
  • 1
Time to create page: 0.074 seconds

I jumped and started to work on a demo component... but 2 days later this demo component became the real component. I just showed today the end result to my customer and he turned to me and said... "this is more than I expected"... All of this is because Cook did cut about 70% of my work and provided me more ways to improve the usability of the component. The end result was 17 tables all related between than to generate a full dashboard for the travel agents. Thanks for Cook developers for such great tool. This component would not be possible to be done at short time with all the features in it
Griiettner (Forum)  

Get Started