-
-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blueprint/Entry/CP Bugs #10598
Comments
Hmm, I'm not sure what's happening. No one else has reported these issues before 🤔 What does your |
My AppServiceProvider.php :::
|
Okay, that all looks fine. 🤔 Are you able to give us access to the repository so we can take a look? Are you able to replicate the issue on a fresh Statamic install? |
Could I send you my repository in private in .zip ? My project is not here in github, it's in my company private repository. |
Sure. You can send it to [email protected]. |
Hmm, strangly enough, even using the site you sent over, I'm not seeing any of the issues you pointed out. Adding/editing fields in blueprints and fieldsets work as expected. Saving entries works as expected (the payload is valid JSON, unlike the screenshot you provided). The actions on the listing table are showing correctly. I'm also not seeing any errors in my browser console or in the Laravel log file. Do these issues happen locally for you, or only on production? |
Since we're not able to reproduce the issue on the repository you sent over, it probably means it's something to do with your local/server setup, rather than Statamic. As I haven't heard back in over a month, I'm going to close this issue for now. |
Bug description
Hi guys! I'm having some issues with the CP can someone help me?
First error is happening on the blueprints. When I try to create new fields and edit the blueprint, i get some errors:
3 Created fields just not appear.
Infinite loading:
Error in the console:
So I just close and open again multiple times, and click to save multiple times until it finally works.
Also I'm getting a lot of errors related to saving the field. When creating an Entry for example, I get the error "Couldn't save entry", but it ends up saving it, and when I try to save it again it says that it already exists.
Then, I decided to take a peak in the console and this was the JSON being sent in the request:
Is this JSON correct? It looks weird.
Some more console errors:
Tried to delete and got this:
Tried again:
It was deleted on the first try, althought presented error.
Also having a little bug when selecting entries to delete. The bar with options just looks like this:
Just some extra details:
-It's happening in more than one browser. Tested it on Edge and Chrome.
How to reproduce
I don't know if everyone is getting these errors, but to reproduce it just act normally, create blueprints, entrys, taxonomies, edit fields in blueprints, try to save entries and blueprints.
Logs
Magically, there's nothing in laravel logs. I caught some errors on the console of DevTools related to JS properties as you can see in the description. Reproduced all error with the laravel logs opened and nothing.
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: