OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki



OJS 2.4.0 Released

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

Forum rules
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 subforum.

Re: OJS 2.4.0 Released

Postby asmecher » Thu Sep 06, 2012 2:08 pm

Hi Ojser,

You need to follow these instructions carefully. You're missing the "-" to the "-p1" option and the pipe is pointing the wrong way (">" instead if "<"); this won't work and likely deleted the contents of the patch file you were trying to use.

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 8581
Joined: Wed Aug 10, 2005 12:56 pm

Re: OJS 2.4.0 Released

Postby Ojser » Fri Sep 07, 2012 3:22 pm

Hi Alec,

Here I made a mistake, but I provided it as indicated in the upgrade notice, but it didn't work.
I'd pose my question from an opposite direction: if I make a new installation with OJS240, and I'd import the journals and/or configuration I've already made with OJS237, will this work correctly?
In other word, which folders that I can import from the old version (ojs237) to the new one (ojs240) to keep my config and avoid to work on again?

Thank you
Ojser
 
Posts: 152
Joined: Wed Mar 28, 2012 6:23 am

Re: OJS 2.4.0 Released

Postby asmecher » Fri Sep 07, 2012 3:30 pm

Hi Ojser,

If you've made any modifications to the code, then that approach won't preserve them.

If that's OK, you'll need to bring your "public" subdirectory and configuration file to the new installation. Note that the configuration file will still refer to your old database and files_dir; if that's OK, then you're ready to go. If not, you can duplicate those and put the new locations into your new configuration file. Then work on the database upgrade process according to docs/UPGRADE.

Note that you'll probably have to correct your file permissions after you do this. The file permission requirements haven't changed between OJS 2.3.x and 2.4.0, but by copying files around you'll probably disturb them.

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 8581
Joined: Wed Aug 10, 2005 12:56 pm

Re: OJS 2.4.0 Released

Postby Ojser » Fri Sep 07, 2012 8:43 pm

Thanks Alec. I'd give it a try.
If you've made any modifications to the code, then that approach won't preserve them.

If I should keep the new files in OJS2.4 and import the unchanged files from ojs237, is there an "easy" way to know which files that have been changed?
My idea is to install OJS240 and import the unchanged files from OJS237 to replace the corresponding ones in OJS2.4 (a kind of partial backup after ungrade). This might help keeping any modifications made in the old version. If the changed files are not so many, this couldn't be feasible manually, by copy/paste/replace? It may be a laborious task, but no choice!
Ojser
 
Posts: 152
Joined: Wed Mar 28, 2012 6:23 am

Re: OJS 2.4.0 Released

Postby asmecher » Sat Sep 08, 2012 12:44 pm

Hi Ojser,

The GNU diff and patch tools are there to do exactly what you describe (and that's why one of the upgrade paths we suggest makes use of them); however, you'll have to do some reading to find out how they work.

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 8581
Joined: Wed Aug 10, 2005 12:56 pm

Re: OJS 2.4.0 Released

Postby Ojser » Sat Sep 08, 2012 12:56 pm

Hi Alec,

Well ,I tried to start from scratch:
I installed a new copy of WAMP (php 5.4.3, Mysql 5.2.24) side-by-side with old WAMP in a new folder, but I still have exactly the same problem: a blank screen!
Strange, isn't t?
Why a new installation doesn't solve the problem, given everything is fresh?
Ojser
 
Posts: 152
Joined: Wed Mar 28, 2012 6:23 am

Re: OJS 2.4.0 Released

Postby asmecher » Sat Sep 08, 2012 2:57 pm

Hi Ojser,

As Jason has pointed out, it's probably an issue with file permissions, just as you encountered when you first installed a previous release of OJS (this requirement hasn't changed). Alternately, perhaps you're encountering http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=7848.

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 8581
Joined: Wed Aug 10, 2005 12:56 pm

Re: OJS 2.4.0 Released

Postby Ojser » Sat Sep 08, 2012 4:03 pm

Thanks Alec,

Yes, I've encountered an installation problem the first time I used OJS but it was different from now. It wasn't a blank screen.
Anyway, how to be sure that it is a file permission issue?
Is there a way to check it and be sure about that? Where to see permission rule related to OJS in localhost?
As far as I remember I didn't set any permission rules. I've started a new installation of wamp and ojs versions without touching any parameters.
I'm trying with default settings.
I thought that installing a new wamp copy will fix the problem but it didn't.


Regards
Ojser
 
Posts: 152
Joined: Wed Mar 28, 2012 6:23 am

Re: OJS 2.4.0 Released

Postby Ojser » Sat Sep 08, 2012 4:43 pm

In case it may help, here are the logs:

- Mysql log:

Code: Select all
120908 21:28:25 [Note] Plugin 'FEDERATED' is disabled.
120908 21:28:25 InnoDB: The InnoDB memory heap is disabled
120908 21:28:25 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120908 21:28:25 InnoDB: Compressed tables use zlib 1.2.3
120908 21:28:25 InnoDB: Initializing buffer pool, size = 128.0M
120908 21:28:25 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
120908 21:28:25  InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
120908 21:28:26  InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
120908 21:28:27  InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
120908 21:28:29  InnoDB: Waiting for the background threads to start
120908 21:28:30 InnoDB: 1.1.8 started; log sequence number 0
120908 21:28:30 [Note] Server hostname (bind-address): '(null)'; port: 3306
120908 21:28:30 [Note]   - '(null)' resolves to '::';
120908 21:28:30 [Note]   - '(null)' resolves to '0.0.0.0';
120908 21:28:30 [Note] Server socket created on IP: '0.0.0.0'.
120908 21:28:33 [Note] Event Scheduler: Loaded 0 events
120908 21:28:33 [Note] wampmysqld: ready for connections.
Version: '5.5.24-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
120908 21:40:20 [Note] wampmysqld: Normal shutdown

120908 21:40:20 [Note] Event Scheduler: Purging the queue. 0 events
120908 21:40:20  InnoDB: Starting shutdown...
120908 21:40:20  InnoDB: Shutdown completed; log sequence number 1595675
120908 21:40:20 [Note] wampmysqld: Shutdown complete

120908 21:43:11 [Note] Plugin 'FEDERATED' is disabled.
120908 21:43:11 InnoDB: The InnoDB memory heap is disabled
120908 21:43:11 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120908 21:43:11 InnoDB: Compressed tables use zlib 1.2.3
120908 21:43:11 InnoDB: Initializing buffer pool, size = 128.0M
120908 21:43:11 InnoDB: Completed initialization of buffer pool
120908 21:43:11 InnoDB: highest supported file format is Barracuda.
120908 21:43:11  InnoDB: Waiting for the background threads to start
120908 21:43:12 InnoDB: 1.1.8 started; log sequence number 1595675
120908 21:43:13 [Note] Server hostname (bind-address): '(null)'; port: 3306
120908 21:43:13 [Note]   - '(null)' resolves to '::';
120908 21:43:13 [Note]   - '(null)' resolves to '0.0.0.0';
120908 21:43:13 [Note] Server socket created on IP: '0.0.0.0'.
120908 21:43:13 [Note] Event Scheduler: Loaded 0 events
120908 21:43:13 [Note] wampmysqld: ready for connections.
Version: '5.5.24-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
120908 21:43:30 [Note] wampmysqld: Normal shutdown

120908 21:43:30 [Note] Event Scheduler: Purging the queue. 0 events
120908 21:43:30  InnoDB: Starting shutdown...
120908 21:43:31  InnoDB: Shutdown completed; log sequence number 1595675
120908 21:43:31 [Note] wampmysqld: Shutdown complete

120908 21:46:50 [Note] Plugin 'FEDERATED' is disabled.
120908 21:46:50 InnoDB: The InnoDB memory heap is disabled
120908 21:46:50 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120908 21:46:50 InnoDB: Compressed tables use zlib 1.2.3
120908 21:46:51 InnoDB: Initializing buffer pool, size = 128.0M
120908 21:46:51 InnoDB: Completed initialization of buffer pool
120908 21:46:51 InnoDB: highest supported file format is Barracuda.
120908 21:46:51  InnoDB: Waiting for the background threads to start
120908 21:46:52 InnoDB: 1.1.8 started; log sequence number 1595675
120908 21:46:53 [Note] Server hostname (bind-address): '(null)'; port: 3306
120908 21:46:53 [Note]   - '(null)' resolves to '::';
120908 21:46:53 [Note]   - '(null)' resolves to '0.0.0.0';
120908 21:46:53 [Note] Server socket created on IP: '0.0.0.0'.
120908 21:46:53 [Note] Event Scheduler: Loaded 0 events
120908 21:46:53 [Note] wampmysqld: ready for connections.
Version: '5.5.24-log'  socket: ''  port: 3306  MySQL Community Server (GPL)


- Apache error log:

Code: Select all
[Sat Sep 08 21:28:24 2012] [notice] Apache/2.2.22 (Win32) PHP/5.4.3 configured -- resuming normal operations
[Sat Sep 08 21:28:24 2012] [notice] Server built: May 13 2012 13:32:42
[Sat Sep 08 21:28:24 2012] [notice] Parent: Created child process 3896
[Sat Sep 08 21:28:25 2012] [notice] Child 3896: Child process is running
[Sat Sep 08 21:28:25 2012] [notice] Child 3896: Acquired the start mutex.
[Sat Sep 08 21:28:25 2012] [notice] Child 3896: Starting 64 worker threads.
[Sat Sep 08 21:28:25 2012] [notice] Child 3896: Starting thread to listen on port 80.
[Sat Sep 08 21:28:25 2012] [notice] Child 3896: Starting thread to listen on port 80.
[Sat Sep 08 21:35:06 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp2/www/favicon.ico
[Sat Sep 08 21:35:11 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp2/www/favicon.ico
[Sat Sep 08 21:37:22 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp2/www/favicon.ico
[Sat Sep 08 21:37:45 2012] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Sat Sep 08 21:37:45 2012] [notice] Child 3896: Exit event signaled. Child process is ending.
[Sat Sep 08 21:37:46 2012] [notice] Child 3896: Released the start mutex
[Sat Sep 08 21:37:47 2012] [notice] Child 3896: All worker threads have exited.
[Sat Sep 08 21:37:47 2012] [notice] Child 3896: Child process is exiting
[Sat Sep 08 21:37:47 2012] [notice] Parent: Child process exited successfully.
[Sat Sep 08 21:37:47 2012] [notice] Apache/2.2.22 (Win32) PHP/5.4.3 configured -- resuming normal operations
[Sat Sep 08 21:37:47 2012] [notice] Server built: May 13 2012 13:32:42
[Sat Sep 08 21:37:47 2012] [notice] Parent: Created child process 6080
[Sat Sep 08 21:37:47 2012] [notice] Child 6080: Child process is running
[Sat Sep 08 21:37:47 2012] [notice] Child 6080: Acquired the start mutex.
[Sat Sep 08 21:37:47 2012] [notice] Child 6080: Starting 64 worker threads.
[Sat Sep 08 21:37:47 2012] [notice] Child 6080: Starting thread to listen on port 80.
[Sat Sep 08 21:37:47 2012] [notice] Child 6080: Starting thread to listen on port 80.
[Sat Sep 08 21:37:56 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp2/www/favicon.ico
[Sat Sep 08 21:37:58 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp2/www/favicon.ico
[Sat Sep 08 21:38:45 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp2/www/favicon.ico
[Sat Sep 08 21:39:45 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp2/www/favicon.ico
[Sat Sep 08 21:40:04 2012] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Sat Sep 08 21:40:04 2012] [notice] Child 6080: Exit event signaled. Child process is ending.
[Sat Sep 08 21:40:05 2012] [notice] Child 6080: Released the start mutex
[Sat Sep 08 21:40:06 2012] [notice] Child 6080: All worker threads have exited.
[Sat Sep 08 21:40:06 2012] [notice] Child 6080: Child process is exiting
[Sat Sep 08 21:40:06 2012] [notice] Parent: Child process exited successfully.
[Sat Sep 08 21:43:10 2012] [notice] Apache/2.2.22 (Win32) PHP/5.4.3 configured -- resuming normal operations
[Sat Sep 08 21:43:10 2012] [notice] Server built: May 13 2012 13:32:42
[Sat Sep 08 21:43:10 2012] [notice] Parent: Created child process 5144
[Sat Sep 08 21:43:11 2012] [notice] Child 5144: Child process is running
[Sat Sep 08 21:43:11 2012] [notice] Child 5144: Acquired the start mutex.
[Sat Sep 08 21:43:11 2012] [notice] Child 5144: Starting 64 worker threads.
[Sat Sep 08 21:43:11 2012] [notice] Child 5144: Starting thread to listen on port 80.
[Sat Sep 08 21:43:11 2012] [notice] Child 5144: Starting thread to listen on port 80.
[Sat Sep 08 21:43:18 2012] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Sat Sep 08 21:43:18 2012] [notice] Child 5144: Exit event signaled. Child process is ending.
[Sat Sep 08 21:43:19 2012] [notice] Child 5144: Released the start mutex
[Sat Sep 08 21:43:20 2012] [notice] Child 5144: All worker threads have exited.
[Sat Sep 08 21:43:20 2012] [notice] Child 5144: Child process is exiting
[Sat Sep 08 21:43:20 2012] [notice] Parent: Child process exited successfully.
[Sat Sep 08 21:46:50 2012] [notice] Apache/2.2.22 (Win32) PHP/5.4.3 configured -- resuming normal operations
[Sat Sep 08 21:46:50 2012] [notice] Server built: May 13 2012 13:32:42
[Sat Sep 08 21:46:50 2012] [notice] Parent: Created child process 2552
[Sat Sep 08 21:46:51 2012] [notice] Child 2552: Child process is running
[Sat Sep 08 21:46:51 2012] [notice] Child 2552: Acquired the start mutex.
[Sat Sep 08 21:46:51 2012] [notice] Child 2552: Starting 64 worker threads.
[Sat Sep 08 21:46:51 2012] [notice] Child 2552: Starting thread to listen on port 80.
[Sat Sep 08 21:46:51 2012] [notice] Child 2552: Starting thread to listen on port 80.
[Sat Sep 08 21:47:20 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp2/www/favicon.ico
[Sat Sep 08 21:47:21 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp2/www/favicon.ico
[Sat Sep 08 21:48:49 2012] [error] [client 127.0.0.1] File does not exist: C:/wamp2/www/favicon.ico


- PHP error log is empty!
Ojser
 
Posts: 152
Joined: Wed Mar 28, 2012 6:23 am

Re: OJS 2.4.0 Released

Postby Ojser » Sun Sep 09, 2012 9:30 am

Why php error are disabled?
I turned php-report error ON but PHP log is still empty!
Ojser
 
Posts: 152
Joined: Wed Mar 28, 2012 6:23 am

Re: OJS 2.4.0 Released

Postby Ojser » Mon Sep 10, 2012 5:57 am

Back again to this post.
I tried to install OJS240 in new machine with new WAMP server but always the same problem: Blank page!
Two copies of wamp, two PC (with windows 7), with database debug error turns On, and the error still the same: blank page without any other error message!
To test if the problem come from my settings, I installed Wordpress with the same database and it works!
What could be the problem with my OJS240?
Damned me!
Ojser
 
Posts: 152
Joined: Wed Mar 28, 2012 6:23 am

Re: OJS 2.4.0 Released

Postby asmecher » Mon Sep 10, 2012 7:54 am

Hi Ojser,

Try the same procedure with OJS 2.3.7. If it also gives you a blank page, then that's a pretty strong hint that it's something in your setup (like permissions, as I've suggested several times). If 2.3.7 installs OK but 2.4.0 gives you a blank page, then it's something different with the new version.

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 8581
Joined: Wed Aug 10, 2005 12:56 pm

Re: OJS 2.4.0 Released

Postby Ojser » Mon Sep 10, 2012 9:13 am

Hi Alec,

OJS237 did installed fine as well as WordPress or other php based programs tested.
The problem is so with ojs240.
I tried to enable all error_reporting codes and here is what I got in the browser page:

Code: Select all
Server error
The website encountered an error while retrieving http://localhost/ojs240/index.php/index/install/install. It may be down for maintenance or configured incorrectly.
Here are some suggestions:
Reload this webpage later.
HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request.


Do you see any clue in this error? and where I can check the permission?

Regards
Ojser
 
Posts: 152
Joined: Wed Mar 28, 2012 6:23 am

Re: OJS 2.4.0 Released

Postby Ojser » Mon Sep 10, 2012 9:59 am

Well, maybe the solution is closer now!
After a fresh installation of OJS 2.3.7 , I replaced all its files by those of OJS240 except the config.inc.php. but there is still a problem: when I check the version (system info) it is still OJS 2.3.7!
How is that? Does this mean that I have to change it manually?
Ojser
 
Posts: 152
Joined: Wed Mar 28, 2012 6:23 am

Re: OJS 2.4.0 Released

Postby asmecher » Mon Sep 10, 2012 10:44 am

Hi Ojser,

That's because you haven't updated the database. See docs/UPGRADE.

Did you try my suggestion above (viewtopic.php?f=8&t=9009&start=15#p35076)?

Regards,
Alec Smecher
Public Knowledge Project Team
asmecher
 
Posts: 8581
Joined: Wed Aug 10, 2005 12:56 pm

PreviousNext

Return to OJS Technical Support

Who is online

Users browsing this forum: Bing [Bot] and 3 guests