Utilities module will not create a new company

[timschofield]

Many of these utilities including this one are out of date. You can create a new company using the installer by going to install/index.php

Perhaps it's worth linking the utilities item to the installer, but getting it to miss out new install specific things (licence etc)

Tim

[efeoli]

It wasn’t necessary. The utility is now working perfectly. I have created on my imported database version, a new last commit fresh install.

Now I can compare both scenarios. Issue is solved.

[efeoli]

Same problem with currencies to be found in the fresh install, if update for currencies is set to automatic.

[dalers]

@timschofield:

Many of these utilities including this one are out of date. You can create a new company using the installer by going to install/index.php

Perhaps it's worth linking the utilities item to the installer, but getting it to miss out new install specific things (licence etc)

Could the installer be re-configured into two parts?

• Part A - create a minimal config.php
• Part B - create and configure a database (and optionally install demo data).

Imho it is reasonable a webERP admin user might want to create a new database without involving their server admin (mostly likely to create a new test or sandbox database, and optionally to populate it with data from another database). I would expect either the dbms root password would have to be entered to be used temporarily to create the database, or a username/password the server administrator configured for this purpose would be needed.

@efeoli

It wasn’t necessary. The utility is now working perfectly.

the Z_CreateNewCompany.php script does not work on my system. I logged into a new configured database as a user with System Administrator role and ran [Main Menu > Utilities > Maintenance > Make New Company].

Attempt 1 - I selected "Create Database" expecting an error message knowing the specified database did not already exist and the database user in config.php does not have permission to create a database. However no error was shown on the page, although a new company directory was created in /companies/ and as expected the database was not created. The links to "Set Up New Company Details", "Set Up Configuration Details" and "Set Up User Accounts" all produced "page not found".

Attempt 2 - this time I manually created the database before running the script, but again no error was output and no tables were created in the database. This time the links to "Set Up New Company Details", "Set Up Configuration Details" and "Set Up User Accounts" produced output but the pages did not appear to fully render - presumably due to errors.

Fwiw, I had to delete my brower cache after each attempt for the webERP server to respond again.

I did not test behavior entering the dbms root user in config.php because Imho webERP should not need root privileges.

[efeoli]

Hi, I did create the new company using the [Main Menu > Utilities > Maintenance > Make New Company] command, but on a previously imported database linked to the user of the original installation. That works very well and avoids the "Set Up New Company Details", "Set Up Configuration Details" and "Set Up User Accounts" steps. One just logs in a different browser and since credentials are the same it just works for our purposes. That is, sharing information with branches not in the same territory and keeping GMP standards across borders. So I apologize if I assumed this to be for everyone.

I fully agree with your findings which indeed are present and frustrating, so perhaps the idea of the 2 step installer would simplify the company creation for new users.

What I would like to emphasize is the enormous value of the example that I mention above. It’s so much more webERP than having a sandbox handy and performs tremendous work when doing multilingual work with the integrated wiki (dokuwiki in our case) and how this makes webERP so special.

I suggest perfecting this feature and as you suggest simplifying it also. Enrique

[dalers]

@efeoli

enormous value of the example that I mention above

Iiuc and based on my experience, in your scenario it seems the only purpose of "Make New Company" is to create a new company directory (.../companies/newcompany/, by copying .../companies/weberpdemo/ iiuc) because the database had already been created.

If you are using phpMyAdmin or similar to manage databases, it seems this enables creating new companies without needing to use the command line. Is this the primary advantage?

[timschofield]

My plan is to abstract parts of the installer into functions such as CreateDBStructure() AddEssentialData() CreateCompanyDir() and then these functions would then be called by the Z_CreateNewCompany.php script.

Otherwise every time the installer changes the Z_* script also needs changing.

Tim

On Tue, 26 Nov 2024 at 18:50, Dale Scott @.***> wrote:

enormous value of the example that I mention above

Iiuc and based on my experience, it seems in this case the only purpose of "Make New Company" is to create a new company directory (.../companies/newcompany/, I believe by copying .../companies/weberpdemo/ iiuc) because the database had already been created. If you are using phpMyAdmin or similar to manage databases, it would appear there is no need for the command line to create a new company. Do I understand this correctly?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>

-- www.weberp.org @TimSchofield2 Blog: https://kwamoja.home.blog/