Supabase plugin VS new supabase backend integration

[Hugo-OC]

Hey,

I recently tried to use the select action from supabase but it returned 0 rows,
after contacting the support this happens to be because I was still using the old supabase plugin instead of the new backend and was advised to switch.

The issue is that the new backend (which I am required to use as now I can’t even make a simple select query ( using only no-code)) work entirely differently that the old plugin was, all my collections are gone, everywhere I was using the user.isAuthenticated variable (which I use a lot of course ) point to an unknown variable, all my workflow actions from the plugin are broken.

As a user that used weweb only for the frontend, I am quite disappointed to see that I am this much impacted by an update that I am not going to use that much (while I completly understand that for a lot a users the new full stack approach is great).

I think it’s faire to ask that I would like the transition to be easier since now I’ve to make some serious work into making this change happens.
Maybe by creating a migration tool/ process to replace the previous plugin by the new backend everywhere it’s used automatically.

This is the objective of this post, to know if I am the only one thinking that, if you are a user in a similar situation as me please show interest in that post (like/comment) to let Weweb team know the importance of that matter.

Thank you

PS : after some recents testing the issue that I mentionned on the supabase select action is now fixed

[RPAL]

Agreed. There needs to be a way to hide everything related to WeWeb backend if we have no intention of using it. The new UI is now bloated with things I have no use for and the front end features I was relying on have been obfuscated or removed entirely.

[Yaj]

Wait how come you have to use the new backend? I don’t understand that.

But you’ve raised a valid point or concern for anyone moving from legacy backend to the new backend. @Joyce What happens if someone moves from legacy to the new backend, would they have to redo all their workflow actions? As I currently understand the system it seems like this would be the case.

[Hugo-OC]

Hey,

Currently, if I try to use the workflow action « select » from Supabase, it’s not working (only using the anon token). The support told me that this wasn’t a bug and that to fix this I needed to migrate to the new backend.

[Yaj]

That’s actually completely false you still can use the old supabase method.

To use the previous method you have to configure your plugins when on interface tab and in the plugins section of the nav bar

You also need to remove that connection to the backend one as once you configure the interface plugin you’ll have duplicate actions for Supabase. To do this go to the Data & API tab and find the integrations section on the nav and disconnect supabase

You can also find this information in these 2 posts I made in the main update thread

WeWeb is full-stack

Any chance the old filters for logs can be put back in to the debug logs. I love the new logs btw, they are better in every way than the old logs, but being able to filter by errors etc was such a good feature with the old logs, I used it personally all the time. Would be great if this functionality could be added back in. [image] Also this new position for preview is already getting really annoying, if you move to the preview button to click while in edit mode and accidently hover over the u…

WeWeb is full-stack

This is actually the wrong place to do your auth. Its confusing but this is for the new plans with the backend support. You need to find plugins on the sidebar to edit the old auth plugin. [image]

At least this should work from my own experience messing around with the Data & API tab.

[Hugo-OC]

I just tested it again, and indeed, the issue mentioned regarding the select action has been fixed.

Thanks for the update