Support Policy (No Support)

*** We are not able to provide any support for a while. *** Please ignore the following.

There's a difference between what is considered support & customizationWe can only provide support on our Osclass templates and plugins. Officially, we will not offer help on customization of our osclass templates. Support is provided for our osclass templates as they are intended to function out of the box. Anything that changes the way they look or function by default is considered customization.

If time allows, we may try to help you with customizations if they are very easy to do, involves only a few lines of code and do not require a lot of time to complete. However, you should not count on it because we officially do not offer help on customization.

The scope of our support includes the following:

  • solving issues with template installation
  • solving template's built-in functionality that does not work (i.e. popup login form)
  • solving issues on bundled osclass modules (i.e. facebookmodule)
  • very basic CSS and styling adjustments
  • bugs fixing
  • fixing Osclass compatibility issues

The scope of our support DOES NOT include:

  • customizing and modifying the template
  • solving on any errors relating to template customization
  • fixing on any broken styling as a result of template customization
  • adding new features or extending current available features & functionality
  • solving issues for osclass modules/plugins not bundled with our template
  • customizing and modifying Osclass modules' templates to match our templates' design
  • general osclass support (please use the osclass support  for that)

With every support request, we will try to respond as soon as possible and solve the issue within our first response. In cases that we cannot do that in time, please be patient. For sure, we're trying to come up with a solution.

Warning: Unknown: write failed: Disk quota exceeded (122) in Unknown on line 0Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct () in Unknown on line 0