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.


Add a new development ticket



Important information relating to your chosen ticket type

If you need us to access your server 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.

Priority

Please select a priority. Pricing for the different priorities is shown in a table here.






If you don't need a fast response and are reporting a definite bug or some feedback, open a free ticket. A commercial ticket will be charged/due-for-payment if you agree to the quote we give, if you tell us to work immediately without a quote, or if the quote would be the minimum for the ticket priority selected.

If you want us to work immediately without providing a quote then you need to ensure you have a good number of support credits in your account to back up the work; otherwise you will need to make sure you have enough credits to match the quote.


Guidelines

Please follow the following guidelines when you post your ticket:

  1. Give your ticket a clear title that summarises the issue. Stick to one issue per ticket. For a full guide, see our guidance document.
  2. Be careful with your English spelling and grammar, make sure you give a clear description, use the correct terminology, and make sure you aren't using ambiguous language. You will save money if we can easily read through your ticket.
  3. If you already have a ticket for this work/issue don't create a new ticket. It is important to stay within one ticket to ensure the assigned staff member is aware of past progress on that ticket.
  4. Your ticket needs to be completely self-explanatory. If it is necessary to reference another ticket please ensure that the exact title of the ticket is given. Different members of staff may work on different tickets so we won't necessarily know the details relating to other tickets.

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