-
Notifications
You must be signed in to change notification settings - Fork 0
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
layout bits #5
Comments
@CFanselow, regarding #5 (comment) -- try checking out the |
@asmecher, could it be that those changes (wehn rebased with the PKP master branches) break the layout when the user is logged in? Or is it something wrong on my side? |
Thanks for this. OMP still has a number of issues like this to work out on the backend. It hasn't had as much testing in the backend as OJS had in the run-up to 3.0 beta, but I do plan a more comprehensive review. I'd expect just about everything to change on the frontend but it's getting a more comprehensive treatment right now. @asmecher What would you recommend to make sure we don't lose track of this? Should an issue be opened on |
Thanks @CFanselow, this one was fixed yesterday. It's the same problem as the fourth screenshot you posted above. |
@NateWr |
Note that if you're experiencing strange layout problems you may need to flush your cache. Delete any |
Regarding #5 (comment) -- I've merged that branch into master; you should be able to get the newest everything by switching back there (for omp and lib/pkp). |
@NateWr, is there a specific comment you're responding to with #5 (comment)? |
@asmecher No that was just a general comment. |
Re: #5 (comment) -- I'd suggest we track it here, but use
That way individual notes can be marked finished. Then as we wrap up this round of testing anything that's not resolved can be moved into the regular issue list on the PKP repository. |
Ok, just that I will probably forget this exists as soon as comments stop coming in. Having it in |
This will backstop it: pkp/pkp-lib#840 |
When deleting a plugin, the locale referencing the display name of the plugin is not found and thus ##plugins.generic.name.displayName## is displayed. |
The plugin deletion key problem mentioned here is noted over at pkp/pkp-lib#1523. |
a number of small layout issues
The text was updated successfully, but these errors were encountered: