-
-
Notifications
You must be signed in to change notification settings - Fork 227
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
Modular Content moving to root when saving since v1.3.2 #1059
Comments
I'm not able to replicate. Which browser are you using? Can you also try clearing the browser cache? |
I cannot replicate too. Using latest Grav + Admin + Cleared Browser Cache (Firefox 52.0.2). |
I also updated to latest version and running with MAMP + Chrome I was able to save modular pages a-ok. |
Could this be because the type of template changed inadvertently? One thing I noticed with Grav + Admin, from source, last night was that the field-select for template would jump back to Default from Modular on occasion, but I haven't tested whether it occurs beyond my out-of-date Chrome. |
The Problem @OleVik mentioned happened to me too! I'm using Chrome V58 |
Hmm.. i did 'fix' an issue yesterday to return Could this be the issue? |
Ok, I think this might need a little JS work to fix. It's resetting to |
Ok, looked into it a little more. Seems this getChildType always returns But seems this is a fundamental new thing that changes behavior since Grav 1.1.17. We'll look into how best to sort it. |
Great! Thanks. I'll test the fix as soon as it's out. |
Ok I can replicate the change of the page template. Looking into it. |
Since the newest update, there's a serious problem with the admin plugin.
as soon as i save some modular page/content the module gets moved outside the parent to the ROOT of the grav pages folder. Unfortunately i have no screenshot, because i already moved back to v1.3.1, but this happened to every module i saved.
The text was updated successfully, but these errors were encountered: