As the developers of Open Journal Systems, Open Conference Systems, Open Harvester Systems, and Open Monograph Press, the PKP team are experts in helping journal managers and conference organizers make the most of their online publishing projects. PKP Publishing Services offers support for:

As a customer of PKP Publishing Services, you will not only receive direct, personalized support from the PKP Development Team, but will be contributing to the ongoing development of the PKP applications. All funds raised by PKP Publishing Services go directly toward enhancing our free, open source software. For more information, please contact us.

Forum rules
This forum is meant for general questions about the usability of OJS from an everyday user's perspective: journal managers, authors, and editors are welcome to post questions here, as are librarians and other support staff. We welcome general questions about the role of OJS and how the workflow works, as well as specific function- or user-related questions.

What to do if you have general, workflow or usability questions about OJS:

1. Read the documentation. We've written documentation to cover from OJS basics to system administration and code development, and we encourage you to read it.

2. take a look at the tutorials. We will continue to add tutorials covering OJS basics as time goes on.

3. Post a question. Questions are always welcome here, but if it's a technical question you should probably post to the OJS Technical Support subforum; if you have a development question, try the OJS Development subforum.

wow, glad this is only the test server, not something I want to experience live.

All the custom settings I inputted yesterday do not show up. Custom header gifs, logo's, custom colour, footer tags, submission sections, etc do not display. I seem to be returned to the install state.

One of my journal article files are intact in the seperate folder (the first test article). I can not bring them up on a search or by going to the journal home page.

I cannot log in as root, editor or author.

Two things happened today:

While looking at the OJS files I noticed my install.php, upgrade.php and xmlimport.php had not been changed to the disabling .bak extension. I did so and after discovering the problem returned them to their .php extensions.

Shaw changed my dynamic at home ip address to a completely different series.

All the custom settings I inputted yesterday do not show up. Custom header gifs, logo's, custom colour, footer tags, submission sections, etc do not display. I seem to be returned to the install state.

One of my journal article files are intact in the seperate folder (the first test article). I can not bring them up on a search or by going to the journal home page.

I cannot log in as root, editor or author.

It sounds like OJS can simply not connect to your database (e.g., the database server is not running, or the settings in include/db.php are incorrect).

While looking at the OJS files I noticed my install.php, upgrade.php and xmlimport.php had not been changed to the disabling .bak extension.

Those files are not required required for a functioning OJS system.

What is that hidden file that is not writeable? I noticed it before.

Unless you actually did not enter a file path during that step of the installation, this behaviour would indicate that OJS cannot connect to your database to retieve that value.

Where are the mirroring instructions for the web application or can I simply just cron to copy both folders (web app, journal documents) to a new server?

Such instructions are beyond the scope of the information we can provide, but unless the journal documents and database were on single servers you would need to ensure somehow that they are synchronized and stay consistent.

Where do the custom files reside?

Directories used for storing uploads include images/custom (journal customization images), images/articleimages (images uploaded for an HTML galley for an article), and the directory you specified during installation to hold submission and related files.