Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.
Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher
What to do if you have a technical problem with OJS:
1. Search the forum
. You can do this from the Advanced Search Page
or from our Google Custom Search
, which will search the entire PKP site. If you are encountering an error, we especially recommend
searching the forum for said error.
2. Check the FAQ
to see if your question or error has already been resolved.
3. Post a question
, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion
subforum; if you have a development question, try the OJS Development
- Posts: 7454
- Joined: Wed Aug 10, 2005 12:56 pm
This OJS Support FAQ is very good thing, but in my opinion it's better to have it on the support page (the one that need to be created and name of the menu will change to just "Support")for OJS divided by sections then at the end of each section it should say "If you are not found the answer pls proceed to the support forum".
Anyway just want to say few words about my PHP CLI importExport.php NativeImportExportPlugin experience. It's not easy to make it work - documentation isn't very complete.
There is no explanation what is journal_path, issue_id and where to get one from usage. And there is no samples with explanation. All things you need to guess. Also import is kind of slow until you change process priority for php.exe to "Above Normal".
Link to short and good manual how to work with PHP CLI will be appreciated. And suggestions where to put issue.xml and from where to run CLI command.
We found that we need to run it from C:\PHP, where php.exe and all dlls are located and issue.xml should be in the same folder:
C:\PHP>c:\php\php.exe -c C:\OJS\tools\php_cli.ini -f C:\OJS\tools\importExport.php NativeImportExportPlugin import issue1.xml Path user_name issue 1
Path is journal path from Home > User > Site Administration > Journals, same as you have in the URL just after index.php/
user_name - name of existing user for the journal
It works only when we change code in the tools\includes\cliTool.inc.php:
Hope this will be helpful for some Windows users.
- Posts: 19
- Joined: Tue Apr 24, 2007 9:16 am
Return to OJS Technical Support
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 4 guests