Class ISPAPI\I18n is already in use

Question

Class ISPAPI\I18n is already in use

Closed this issue 4 years ago · 5 comments

Error Message:
Whoops\Exception\ErrorException: Cannot declare class ISPAPI\I18n, because the name is already in use in /home/managerf/public_html/modules/addons/ispapidomaincheck/lib/Common/i18n.class.php:9
Stack trace:
#0 /home/managerf/public_html/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php(0): WHMCS\Utility\Error\Run->handleError(1, 'Cannot declare ...', '/home/managerf/...', 9)
#1 [internal function]: WHMCS\Utility\Error\Run->handleShutdown()
#2 {main}

Answer 1 · 2019-09-03T21:45:05.000Z

Did you overwrite the files instead of replacing the module? I found removing the previous module before uploading the new one resolved this issue.

…

On Tue, Sep 3, 2019 at 9:11 PM fastsui ***@***.***> wrote: Error Message: Whoops\Exception\ErrorException: Cannot declare class ISPAPI\I18n, because the name is already in use in /home/managerf/public_html/modules/addons/ispapidomaincheck/lib/Common/i18n.class.php:9 Stack trace: #0 /home/managerf/public_html/vendor/whmcs/whmcs-foundation/lib/Utility/Error/Run.php(0): WHMCS\Utility\Error\Run->handleError(1, 'Cannot declare ...', '/home/managerf/...', 9) #1 <#1> [internal function]: WHMCS\Utility\Error\Run->handleShutdown() #2 <#2> {main} — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#104>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKGVNNBQ5XANUWLFKD3O3JDQH3AI3ANCNFSM4ITKMNFQ> .

Answer 2 · 2019-09-03T22:06:09.000Z

Thanks for the Information. Your Solution works for me. But when the Solution is so easy why do you not insert this in the Documentation ?

Answer 3 · 2019-09-04T11:20:44.000Z

@domainregistrar thanks for helping, Dude :-)

@fastsui
We internally have symbolic links in use while developping and also on our test servers. That's the reason why we won't run into such issues. I'll extend the documentation to first delete the old module contents before unpacking the new contents. We have further plans/projects in queue that will solve such issues directly. It just needs time when we get there.

Thanks for getting in touch with us and for bringing this up.

Answer 4 · 2019-09-04T11:28:26.000Z

I've decided to leave this open until we have realised that project, so that we can follow-up.

Answer 5 · 2020-10-29T15:28:10.000Z

We have plans for 2021 to work on a new API that is thought to improve a lot of things especially in direction of 3rd-party software integrations (whmcs, blesta, ...) e.g. minimizing amount of module upgrades etc.. When this API is ready and our modules are refactored, we will have such translations probably available over our API. Therefore I am closing this issue.