SkaDate / Oxwall Troubleshooting : blank white page

You can face blank white page while performing any process in SkaDate / Oxwall software.

Blank white page is indicating that an error occurred BUT your server is configured in a way to hide those errors visually on front end of your site.

If you face  blank white page in SkaDate / Oxwall software:

Continue reading

SkaDate / Oxwall : how to remove “delete” button from profile edit page

Any users ( except site admin) can delete his account from your site using “Delete” button located on Profile Edit page. As site owner you can hide this button to restrict users from deleting their profiles. In this post I will describe how “Delete” button can be completely removed in Oxwall / SkaDate software.

Note: this modification will be erased if you update core platform in future.

Modification type: minor/basic HTML modification.

Continue reading

SkaDate / Oxwall : how to mark all users as verified in database

You can always verify your users’s emails in Admin Panel >> Browser users.
This interface allows to select up to 20 users and verify them at once. To verify more users you will need to repeat the process several times.

When you want to mark a lot of users as verified at once you can run simple mysql query in your database instead of verifying users from Admin Panel:

Continue reading

SkaDate / Oxwall : how to deactivate plugins in database

Deactivate plugins via database only when:

  • you can’t access your admin panel due to an error.
  • you know which plugin is causing the error
  • you were not able to fix the error using other solutions.

Be aware that plugin deactivation will not fix the issue. It will just hide it, so that you can access your admin panel and do further actions to actually resolve the issue.

To deactivate the plugin:

Continue reading

SkaDate / Oxwall Troubleshooting : how to find out whether all of your cron tasks are being executed.

Cron is responsible for many of important features in SkaDate/Oxwall. From reference guide about Cron you already  know that main run.php file executes number of local cron.php files located within the source code of your plugins. It is assumed that any plugin that has cron.php file with scheduled jobs must get executed by Crontab.

Cron execution is a cycle. This means that cron.php files are executed one after another starting with “base” cron. If Cron faces an error along the way, it won’t “jump over” that cron.php file. Cron will just get stuck on that file and will be doing this over and over again.

There are two ways to check where exactly Cron stucks.

Continue reading