I have a complaint ...

So I created a new project from scratch to replace the same project because I know if I don't build everything out a certain way bugs get introduced. So, this time I forgot to select the new Cook 2.0 beta. I built everything out. Before I ever ran it on the Cook sandbox I noticed my error. So I selected 2.0. Then I built the files for the first time.

Guess what? All kinds of access errors. I go back and switch to the old Cook, rebuild, and run in the Cook sandbox. Works fine.

Ok, can you imagine how frustrating it is to spend 6 hours building something to not have it work for something this simple?

Hi @jcbenton,

Firstly, I'm sorry you've experienced this! I've also made that mistake before as have many other users here too and yes, I can therefore understand your frustration.

Have you tried

1. closing all layouts, tables in your project
2. resetting to version 2
3. killing your session in the builder + clear all cache
4. logging back in
5. rebuilding files?

?

Will try now.

Did not work.

Please excuse me for 5 minutes while I throw shit around my office in anger.

OK,
What errors specifically?

I'm just trying to think about what's changed greatly in V2.0... What kind of fields do you have in the project?
Publishing wizard has changed a fair bit - was a bool, now an int
Created/modified by, dateTime & access have changed too.

If you've any of these fields in particular, try

1. removing them from your layouts (maybe just one layout at a time)
2. re-add them
3. rebuild
4. retry that layout in sandbox

Whatever happens, I'm sure that all is not lost and that @admin will be able to salvage any corrupted code for you...

Anyway, hope you get it sorted!

Best of luck,

Gez

PS did you sort out your custom code running on submission of admin form?

Error 500. Permission denied.

I am just rebuilding the entire component. Thank though.

That 500 error is probably because of a misconfiguration of ACL in your params.

That's on the cook sandbox. And that is as administrator. Again, If I change to the old cook it works fine.

That strongly suggests to me that the issue is in having a view access field or publishing wizard that was previously different in 1.5...

Honestly, would be well worth 10 mins to remove any instances of those from just 1 of your tables/layouts, readd them in v2 builder and retry...

If that doesn't work then you've not lost too much.

Gez

Removing the access did clear the error. However, I am going to rebuild the entire thing in the event there is a problem I don't see yet.

Appreciate your help.

Thank you audibeid for your help again.

@jcbenton
I am really confused about your problem. In the same time, I must admin I am really busy.
500, I heard about it one time recenty on the forum.

Some ACL problems might be wrong, and it can be in the builder. I must check your project and tell you something.
Thank for your patience.

Moved in New Ticket.

Hi @admin,

It turned out to be a conflict with the way access worked.

When @jcbenton removed access field and re-added it, it worked.

Gez

Sorry @admin

I think I just deleted your post accidentally!!!

Can you get it back?

Ok, no problem I restored the post.

Do you mean it is solved now ?

I believe so...

I wanted to double check with you but, I believe that the whole issue arose from @jcbenton accidentally building in 1.5 with an access field. When he switched to Cook 2.0 it didn't work and he was getting 500 errors which I've seen when a user has no acl access to a view in the builder. I thought that I read somewhere that this was a security feature in the builder???

In any case, once he'd removed and re-added the access field in v2.0, all was well...

On a slightly separate issue, I wondered if you had chance to view his other post : www.j-cook.pro/forum/7-design-your-appli...nserting-custom-code ?

I wasn't able to find how/where to help him on this and was very curious myself...

Many thanks,

Gez