HTML Logo by World Wide Web Consortium (www.w3.org). Click to learn more about our commitment to accessibility and standards.

Moving forward with Composr

ocPortal has been relaunched as Composr CMS. ocPortal 9 is superseded by Composr 10.

Head over to compo.sr for our new site, and to our migration roadmap. Existing ocPortal member accounts have been mirrored.

Transferring support credits

Purchase of support credits on ocportal.com is closed, but credit may now be purchased on compo.sr. To have your credit transferred please open a support ticket and we will arrange this for you. We will be able to do ocPortal support on compo.sr up until ocPortal v9 reaches its official end of life. We have not migrated over existing tickets.


Report an ocPortal bug (free ticket)



Important information relating to your chosen ticket type

Please make sure you are running the latest stable version of ocPortal (the front page of your Admin Zone will say if you are not) before submitting your ticket. Please do not report errors to ocProducts that are related to third-party addons/modifications.

If your problem looks like it might be caused by a server configuration issue (for example if you are getting an 'Internal server error' message), please check our FAQ first.

If you want us to access your server to better analyse a problem please make sure that you either give FTP (or equivalent) access details in your ticket, or you have set them in your member profile. If you ask or imply we need to access your server you are implying that you agree to our server access policy.

We want to be able to help you fix your problem quickly so please provide full information, as appropriate. For example:

  • your ocPortal version
  • a (copy & pasted) stack-trace, if ocPortal gives one
  • the exact error message
  • a screenshot(s) or Jing screencast
  • any prior actions that might have led to this bug (for example, if you uninstalled an addon and now get error messages that look like they may be related to it)
  • situational details that might be appropriate (for example, if you added news, and it was added as blank, did you get a Comcode error before it, or did you leave a field blank?)
  • any related information, such as module names, in the correct case (e.g. Don't refer to the 'GALLERIES' page instead of the 'galleries' page, because it may mislead us to thinking that a template or language string was in error – as they are in upper case)
  • and anything else you think could help. Fixing bugs is like detective work: clues are vital. There is little more frustrating for us than a bug report that simply indicates there is a problem in a certain regard, without providing any level of detail we can use to trace or reproduce the problem.

If you can't remember a PHP or ocPortal-critical error message, you may be able to find it in your error log (located in the Admin Zone, under the Usage section). The error log shows all non-user-errors that have occurred on your site.

If your report is not clear enough for us to immediately see it as a bug we may require you to post with a commercial ticket and refund you if an investigation proves it was a bug – so please make your reports as clear as possible.

If you are reporting an urgent issue, and need personal attention, consider opening an emergency paid support ticket instead. Bug reports are not intended as a personal support avenue.

Ticket starter-post

Your name:
Subject:
E-mail address:
Your message:




 

You can upload new attachments below. To add one from the file/media library, add an attachment Comcode tag.

New attachment #1

Upload Help


Other tickets by Guest

None