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
Auto-migration issues #3242
Comments
This is likely a result of "dojo" and "gridx" having to be manually added in our current testing scenario, but I'm seeing two filter fields in the Widgets palette: Update: This is #2712. |
Yes, that's a known issue. |
Whereas my simple mobile page using default themes works fine, my simple mobile page WITH A CUSTOM MOBILE THEME doesn't load its CSS themes properly after migration: |
Custom theme or built in theme? |
Custom theme (I amended my note above). |
Poorly formed back arrow on Heading widget in previewer when running Mac/Chrome on a migrated file. @peller (UPDATED) When I change the URL bar to set zazl=false, then arrow renders correctly. Looking in the debugger at various CSS rule defintions, I see that various classnames that are mixed case without zazl (e.g., .mblToolBarButtonText) end up as all lower-case when zazl is active (e.g., .mbltoolbarbuttontext). I don't know CSS rules about case very well, but I suspect that WebKit's inheritance logic requires exact case-sensitive class name matches. |
Tried to open Theme Editor for a custom theme of "custom". I got an error trying to load |
No reviews were carried over for me. Assuming this is what we want for M7. (Might be a different issue in later milestones). |
Error in console on migration page:
Using FF on Mac. |
Yeah, I can't successfully open any of the migrated files that were in an Eclipse project, even after attempting to tell the Modify Libraries pane where Dojo needs to go (i.e., ./WebContent/lib/dojo) |
Didn't take me to my last project (e.g., I was taken to "project1" instead of the one I just created before migration). |
Error in console trying to open file in "project1" and page just spins:
using FF on MAc |
@aerwin, that probably means it's trying to find a disabled library. Check "Modify Libraries" dialog. |
@jhpedemonte you're correct. thanks :) |
After migration, couldn't create another project. Got this in server log:
|
Error opening mobile page in Eclipse project using FF on Mac:
|
Error for mobile page with carousel on page:
Do we at least have something in release notes for the carousel issue? |
I didn't put anything in the release notes. You can see the current release notes by going to Help->Documentation and looking for "Release 7" under release notes. The source file is at maqetta.core.client/WebContent/docs/releaseNotes/release7.html |
I had an issue with my migrated workspace, so I switched over to Orion. I deleted the problem project, then selected one of the remaining projects and selected Open in Maqetta. Nothing happened. No errors in browser console or server log. |
Committed and ran a migration script (see #3256). Most of these issues should be fixed by that. |
I updated the summary, striking out issues that have been fixed by migration script. For Eclipse projects, app.js and app.css still show up outside of WebContents folder. |
Closing this bug. The "samples" discussion can take place in #3256. The other 2 remaining issues are handled in other bugs and don't seem to be migration specific. If you encounter any other migration bugs, open a specific issue. |
Issues:
"dojo" and "gridx" libraries were disabled after migration.Mobile page doesn't load theme.and [2]Failure loading custom theme.Error when creating project.The text was updated successfully, but these errors were encountered: