URLs for Conferences

[tshore]

I have used OCS since 2003 for a couple of different conferences. Here are the URLs that I tend to use.

For the organization's main website:

http://www.imrf.info/

And then, for each year, we use:

http://www.imrf.info/2006/
http://www.imrf.info/2007/

etc.

Of course, for this year's conference, I would like to use:

http://www.imrf.info/2008/

and then continue on with /2009, /2010, ...

When I installed the beta version of OCS 2, I was a bit confused about what directory I should install the application into. That is, in order for my conference URLs to continue to work in the same fashion.

I am now ready to install the real version of OCS 2 (in fact, my client, the conference organizer is MORE than ready for me to install it!) and I would appreciate any advice you can give me.

Thank you.

[asmecher]

Hi tshore,

OCS 2.x uses a different URL scheme. Generally, URLs will look like:

http://[some-url-here]/ocs2/index.php/[confName]/[schedConfName]

...where [some-url-here]/ocs2 is the URL and path to your OCS installation. The later parts in the URL that look like paths ([confName] and [schedConfName]) are not actually directories -- these are passed to the OCS script. OCS can host multiple iterations of multiple conferences, which is why these are present. (In your case, [confName] would be "imrf" and [schedConfName] would be "2008".)

You have several options for maintaining your old URL scheme:

• Install OCS directly in the 2008 directory. This is easiest, but if you later want to host another conference or year in the same installation, you'll have to move it.
• Install OCS in some other directory (e.g. /ocs2) and use redirector scripts to send users to it from the /2008 directory. Put a script called index.php in the 2008 directory with contents like:

  Code: Select all

  <?php header('location: /ocs2/index.php/[confName]/[schedConfName]'); ?>

  (replacing, of course, [confName] and [schedConfName] with the conference and scheduled conference paths you created via the user interface of OCS.)

Regards,
Alec Smecher
Public Knowledge Project Team