|
|
6.
|
|
|
Keep regular backups: even if you make no mistakes and know precisely what you're doing, there could be a fire in your remote data centre, for example.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TIP_1e
|
|
|
7.
|
|
|
If stuck, check the documentation. If you're still stuck, contact ocProducts. You should actually read the documentation anyway as you will find it an enormous help – we have provided general advice on running websites as well as ocPortal-specific advice.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TIP_1f
|
|
|
8.
|
|
|
Please <a href="http://ocportal.com/site/pg/tickets/ticket/index.php&default=Feedback">give feedback</a> to ocProducts so that we may improve things in future versions. It is enormously important to us that your ocPortal experience is as good as we can make it.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TIP_1g
|
|
|
9.
|
|
|
The developers of ocPortal, ocProducts, are available to do work on a commercial basis. If you need new features developed for your website and can budget for it <a target="_blank" href="http://ocportal.com/site/pg/tickets/ticket/index.php&default=Enquiry">consider contacting ocProducts</a>. (If not that's cool too, ocPortal is Open Source so our business model is to serve both the open community and corporate userbases)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TIP_1h
|
|
|
16.
|
|
|
Want to discuss things with other ocPortal users? Visit the <a href="http://ocportal.com/forum/">ocProducts forum</a>.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TIP_1o
|
|
|
28.
|
|
|
Use the Comcode <tt>hide</tt> tag to place messages that are obscured until consciously uncovered. This is great for placing warnings (such as <tt>spoilers</tt> or disclaimers) or hiding answers to questions so to give the reader time to think.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TIP_2l
|
|
|
32.
|
|
|
Regularly change add content to your website, or randomise content display using the <tt>main_content</tt> block. This will keep your visitors returning, which in turn will make them more likely to recommend your website to others.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TIP_2p
|
|
|
33.
|
|
|
You will find the ‘Template tree’ and ‘Language’ options in the list of options in the login block very useful for changing the templates and language strings of the page you are viewing.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TIP_2q
|
|
|
34.
|
|
|
Use the Comcode <tt>page</tt> tag instead of the <tt>url</tt> tag whenever referring to local URLs. By doing this you can gain protection against changes in URL behaviour between versions and the effect on URLs by pages moved between zones.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TIP_3n
|
|
|
36.
|
|
|
Use the ‘SU’ feature to test your site as any user of your choosing. It's easy (regrettably, but inevitably) to make mistakes when setting permissions and lock off an important portion of your site to those that should be able to see it. You can activate ‘SU’ manually by appending <tt>&keep_su=<username></tt> to the URL. ‘SU’ is superior to logging in as another member not just due to speed, but also because you will still be able to see things such as stack traces.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
[strings]TIP_3b
|
