rhiccoyoca Posted March 23, 2015 Posted March 23, 2015 Got several UI messed-up on pop-ups and report viewer.Also, in the report viewer, I cant click on the next pager and other buttons beside it. It seems like there is div element something shadowing above the buttons. Please give me your feedback on how to deal with these bugs. Thanks,Ric
marianol Posted March 24, 2015 Posted March 24, 2015 It looks like you imported and old (pre JRS 6.0) theme into your JRS 6.0.1 instance, is that the case? You may have done this without knowing by importing a full repository from a backup.If that is the case, I attached to this thread a clean JRS 6.0.1 theme. You may need to delete the one you have and upload this theme with the name "default", remember to upload this as a Theme not as a repo import.See screenshot:
srang Posted March 24, 2015 Posted March 24, 2015 I had this exact same problem on a 5.6 aws box I 'inherited' when he rolled off the project and I had no idea how to fix it
marianol Posted March 24, 2015 Posted March 24, 2015 Tell me if this works for you, it should.. if not we can try a repo export of the theme. Next time when you import back the data from your old repo after the upgrade; use the buildomatic scripts with the "--skip-themes" option so this does not happens again. See: https://community.jaspersoft.com/documentation/tibco-jasperreports-server-administrator-guide/v601/import-and-export-through-command scroll down to Importing form the command line.
florent.j Posted June 16, 2015 Posted June 16, 2015 Hi, when I try replacing the default theme by yours I get "Cannot upload the theme : Access is denied" and I cannot delete it manually (even as superuser) any other solution? Thanks, Florent
marianol Posted June 17, 2015 Posted June 17, 2015 Are you using the superuser account for importing the theme? What version of JasperServer for AWS are you using 6.0.1?
jay_01752 Posted June 22, 2015 Posted June 22, 2015 I couldn't delete the old default either, you can still make the supplied theme active.
florent.j Posted July 9, 2015 Posted July 9, 2015 I'm not using JasperServer for AWS but the normal pro one in version 6.0.1 also, I didn't use the superuser account but just a user with superuser rights. Should it be different with really the supruser account? thanks, florent
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now