Support

Kickstart does NOT need built-in PHAR support to execute. If PHAR support is disabled on the server the PHP stub at the start of the file detects it, extract the application inside the kicktemp directory, and executes it as a normal PHP application much like Joomla and WordPress themselves do. You can force this behaviour by creating the kicktemp directory and a nophar.txt file inside it as per our documentation.

If your host does support PHAR, all you need to do is change some OPcache settings as per the documentation. These are also displayed on Kickstart's main page if this potential problem is detected. You can set them up at the hosting account level, or in a .user.ini, php.ini, or .htaccess file depending on how your host runs PHP on their web server.

The only "server restriction" that would disallow Kickstart to run is that your web root is not writeable, or PHP execution is completely disabled. Both of these "server restrictions" would make installing and using Joomla and WordPress impossible. Therefore, either your host is lying to you (possibly because the person you talked does not understand the subject matter well enough), or they are selling you a service that is unsuitable for the purpose you want to use it.

You're welcome! If you have found a host where none of these suggestions work, let me know; I could make the ticket private and take a look myself. There's always a way to make things work. It's what I've been doing the past 20 years I've been publishing this software ;)

What you describe is consistent with an OPcache issue.

You should fix those settings ESPECIALLY if you plan on using Joomla or WordPress on that site. Both CMS update themselves and their installed software by overwriting files. Your current OPcache settings will prevent the new files from being read. In other words, you install an update that fixes a security issue thinking that's the end of it… but your server still runs the old code with the security vulnerability and now your site is hacked. Then you turn around and blame Joomla, WordPress, third party software developers, PHP, and basically everyone and anyone except your host who stupidly chose to keep the default OPcache settings which are geared towards VMs rebuilt on new software deployment instead of standard hosting. Essentially, your host does not seem to know their business model and which market segment they serve. Maybe it's worth considering a switch to a different, more competent host in the not-so-distant future?