Timo, thank you to you and your team for taking this project on for the time you did! Although we don’t use this solution actively anymore, it was still nice to see the progression over your tenure. It is a great example of community participation and you all should be applauded!

Thank you ! - I have a number of clients that actively use this.

Thanks Timo for keeping this module going.

Hi All,

It's unfortunate that it isn't getting upgraded any longer. We use it for our journal and may have to migrate to an Open Journal System (OJS).

There is a broken section in the module under the admin section. I can no longer add a category and save it, which is pretty crucial.

It should look like this:

Now it looks like this and no longer functions! Can't save or scroll anymore.

And this:

Completely useless now.

 

some error messages on the console log

Mixed Content: The page at 'https://journal.nafo.int/...ategory/mid/420' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.c...mily=Open+Sans'. This request has been blocked; the content must be served over HTTPS.
jquery-migrate.js?cdv=337:2 JQMIGRATE: Migrate is installed, version 3.4.1
ckeditor.js:21 [CKEDITOR] Error code: exportpdf-no-token-url.
(anonymous) @ ckeditor.js:21
ckeditor.js:21 [CKEDITOR] For more information about this error go to https://ckeditor.com/docs...portpdf-no-token-url
(anonymous) @ ckeditor.js:21
420:1 Mixed Content: The page at 'https://journal.nafo.int/...ategory/mid/420' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.c...mily=Open+Sans'. This request has been blocked; the content must be served over HTTPS.

It's possible that there are some bad HTTP vs. HTTPS references in the module.  That's an easy fix, if that's the issue.  In the meantime, have you tracked down the HTTP file references to this module, or somewhere else, both?  

There is a 00.13.01 version, did you try that?
I just tested adding a category on my test site (DNN 9.10.2 Module 0.13.01) and it works fine.
I wonder if you might have another issue TBH.

Did you rty if it does work when you switch to the default (Xcillion) Theme for that page?

I don't know what functions of the module you are actively using, but a similar solution in Open Content or 2SXC is also possilbe and way more flexible. (does require more development skills though or you need to ask someone to create the "template" for you)

I don't know where to find them in order to fix them.

This is where it is:

Mixed Content: The page at 'https://journal.nafo.int/...Options/mid/420' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.c...mily=Open+Sans'. This request has been blocked; the content must be served over HTTPS.

Not sure where to find this file and fix it.

1. No label associated with a form field

   1. A <label> isn't associated with a form field.

      To fix this issue, nest the <input> in the <label> or provide a for attribute on the <label> that matches a form field id.

   2. AFFECTED RESOURCES

      1. 8 resources

1. Reading cookie in cross-site context will be blocked in future Chrome versions

   1. Cookies with the SameSite=None; Secure and not Partitioned attributes that operate in cross-site contexts are third-party cookies. In future Chrome versions, reading third-party cookies will be blocked. This behavior protects user data from cross-site tracking.

      Please refer to the article linked to learn more about preparing your site to avoid potential breakage.

2. This page failed to load a stylesheet from a URL.

If I use MS Edge and decrease the screen size, I can see the edit pencil tool. It's at least functioning, but the interface looks bad.

I am hoping to switch our website eventually to another platform for journals. PKP (Public Knowledge Project). We do not have enough developers in our organization to manage some of these technical requirements on the backend.

I suspect this is not an issue of the Ventrian module but of your skin - it is trying to load a web font from the Google API vie http (instead of https). This should be the place to look for.

Anyhow, you can use the CSP (Content Security Policy) to avoid this effect and also long searches for the culprit. See CSP: upgrade-insecure-requests - HTTP | MDN (mozilla.org) for more information.

Happy DNNing!
Michael