4th version is quite different from the previous. There not many new elements, however. It brings new mechanisms for layout development and javascript functionality, and upgrading is quite a headache.
It is nothing more than bootstrap 4 elements integrated into our new theme. We do not want to make it publicly available because it is what makes our journal unique.
Making such design is a matter of Smarty/CSS and Javascript knowledge (latter for functionality). Also, it requires reading and understanding Bootstrap documentation.
Yea, then it make sense to stay with bootstrap 3, cos i have spent many weeks or even months coding for jmri. If i upgrade, high chances that i will screw something up. Lol. But I liked the bootstrap’s navigation bar for mobile phones. It is well organised as compared to that of manuscripts. I will try to incorporate it in the default theme.
I did see, however I couldnt find the error (affix is crossing the footer). Could you just have a look please. https://jmri.org.in/jmri/article/view/66. The bottom-affix is not even called here.
Firstly, you have 3 javascript errors (in browser console); maybe they are causing the problem.
Secondly, in case of jats-manuscript theme, these line of code control top and bottom affix borders:
Where #myAffix is the element id, .affix - bootstrap method, top - top border (for sticky function), bottom - bottom border. $(window).height() - height of the browser window $('div#pkp_content_main') - the element we want to work with offset - jquery method for determine the current position if the element offset.top - position from top
This all works in my case, but if you have done custom changes, you need to update this code accordingly.
Also, your site is loading near 12 sec because of javascript. I recommend checking your files for the redundant code.
@Ph_We, What you mean by that? That you can download JATS XML? That was done deliberately.
Keep in mind that on article landing page you see JATS XML convered to HTML by JATS Parser Plugin.I simply don’t see a need to render JATS XML once more with Lens Viewer.
Or you have something different in mind?
Ah, now I see, sorry, my bad. You had a more traditional layout earlier. So the reader had to click on XML to read a JATS XML version. I tried to show that to my colleague, but could not do that