.htaccess and table prefix in database

Sebastian 2018-02-02 00:02:44 UTC #1

Hi,

I have two question during the install process. My setup is provider-hosted webserver currently running a website. A subfolder was created for eGroupware.

the .htaccess file in eGW seems to need a minor change, I found a little answer to it but would need some more detailed instruction too fully understand it. I changed the filename to _htaccess and I successfully reached the installation page, before it only took me to internal server error 500.
I’m limited to one database in the current subscription and would like the tables for eGW to have a prefix. Is it possible?

Kind regards,

Sebastian

RalfBecker 2018-02-02 07:50:10 UTC #2

renaming .htaccess to _htaccess effectivly disables it
All EGroupware tables have a common prefix egw_, which can not be changed

Shared hosting providers don’t work well with EGroupware, I recommend to get a virtual root-server or use our SAAS services.

Ralf

Sebastian 2018-02-02 07:59:14 UTC #3

Thanks Ralf,

So I don’t need the .htaccess at all or the stuff in it?
That prefix will do alright
Yes, I will probably make that move later but for now just trying out different options for a non-profit organization.

RalfBecker 2018-02-02 08:15:03 UTC #4

The stuff in .htaccess is either needed or at least recommended.

That you get a 500 probably comes from your provider not allowing to change some of them.
Alternatively you can use Setup (http://domain.com/egroupware/setup/) to check for required php.ini settings. It will run automatically if you point your browser to the URL corresponding to your installation directory.

Ralf

Sebastian 2018-02-02 08:21:58 UTC #5

Running the install checker without the .htaccess I get warnings for:
pgsql
pdo_pgsql
ldap
tidy

Everything else is checked green. So it doesn’t seem necessary?

Sebastian 2018-02-02 08:29:59 UTC #6

What would be the correct way modifying .htaccess to get it working?

RalfBecker 2018-02-02 09:47:15 UTC #7

That is why that kind of installation (dumping the archive in the docroot of a shared hoster) is NOT the recommended way to install

*pgsql is only needed if you plan to use PostgreSQL, that’s why it is only yellow (warning) and not red (error).
Same is true for ldap, not needed if you store accounts in the database.

tidy is a different story, it is needed to clean up office documents created by merge-print. But to get a PHP extension you need to talk to your hoster or consult with his documentation.

paulr00001 2018-02-02 18:51:20 UTC #8

.htaccess file is not the problem.

Egroupware has too many special requirements to run on a “shared hosting” setup.