Opening the site editor always calls the Theme selector to open

[guillolb]

I signed up for Weebly last wednesday, I was able to use the site editor, but since thursday I haven't been able to do anything because every time I open the site editor, the theme selector pops up and there is no way to move forward beyond that.

I submitted a support ticket and all I'm told is "sorry you are affected by that bug".

I haven't received any updates or ETAs, but of course, my credit card has already been charged for a service I can't use. 

Site: pontigo.org

[Adam7]

Thanks for posting about this, @guillolb. There is an open bug being worked on by our engineers about this, so I've added your information to that. If you'd like to get updates please contact our Customer Success team and they will make sure that you get notified of when it's fixed.

[Adam7]

Oh, I just re-read your post and saw you've already submitted a ticket. Sorry about that, @guillolb. Hopefully this is resolved quickly for you!

[guillolb]

It's so frustrating. 

I already payed 300 and i can't use the product.

They just told me the same thing.

"No ETA".

I don't understand how it is so difficult to troubleshoot for 6 days.

Something is triggering the theme selector to auto open.

Probably some flag that sets the status of a site as "not built yet".

If that is correct, then there has to be some code that automatically opens the theme selector. All they need to do is disable it and put a button to manually open it until the problem is found.... You know, fix the problem for the customer first, then fix your code.

[guillolb · Accepted solution]

After waiting for 8 days with no resolution from the incompetent people of Tech Support,I called Billing to get a refund, and Ryan (from Billing) figured it out in 10 minutes.

It tuns out that themes based in Unite 2, Birdseye 2 and Oasis have this bug.

Once Ryan figured it out, he switched my theme to a different one to "unlock my site".

[Bernadette3]

That's frustrating @guillolb I'm sorry it took so long for us to come to that conclusion, but glad to hear you are able to work on your site now. Thanks so much for posting the information for others in case they run into the issue as well.