Jump to content

WHMCS Bridge PHP8 and ionCube 12 Compatibility


Go to solution Solved by RadWebHosting,

Recommended Posts

Hi guys,

I am migrating our WHMCS and website front to PHP8.1.

I use WHMCS Bridge to create a sort of iframe in my website that allows clients to log in and see their dashboard directly from my website. The setup is excellent and works really well at the moment, however the plugin doesn't seem to be compatible with PHP8.

When I test it, I get the following fatal error:

wp-content/plugins/whmcs-bridge-sso/sso.init.php encoded as type [1/71] cannot be decoded by this version of the ionCube Loader. in Unknown on line 0

The files used in the bridge plugin are encoded with ioncube 10 and can't be decoded with ioncube 12.

I was wondering if anyone had any possible solution to this?

The developer of the plugin seems to have gone MIA and isn't replying to any support requests. This raises red flags for the future of this plugin, so if anyone has any decent alternatives they can recommend, that would be great (I've already tried WHMPress but that was ever worse when it came to dev support). 

Any assistance would be much appreciated.

Link to comment
Share on other sites

  • Solution
On 12/9/2023 at 7:17 AM, Hays Sleiman said:

The files used in the bridge plugin are encoded with ioncube 10 and can't be decoded with ioncube 12.

I was wondering if anyone had any possible solution to this?

The developer of the plugin seems to have gone MIA and isn't replying to any support requests. This raises red flags for the future of this plugin, so if anyone has any decent alternatives they can recommend, that would be great (I've already tried WHMPress but that was ever worse when it came to dev support). 

Sadly, since Ioncube 10 is not compatible with PHP 8.1 and your module developer has not provided you with the appropriate files (for Ioncube 12 compatibility), then it seems you will be stuck with PHP 7.4.

In my opinion, this type of setup (any that attempts import/framing WHMCS inside of WordPress) is not advisable for numerous reasons, among them:

  1. Security concerns
  2. Performance degradation
  3. Compatibility issues

Sorry if this is not helpful to your current situation.

Link to comment
Share on other sites

Thanks for the reply. I have indeed decided to use the WHMCS frontend instead. I think this is safer for longevity and security as you point out and will have much fewer compatibility issues down the track since I'm not relying on a 3rd party. I just need to align the look and feel of the WHMCS client area with our WordPress theme. Thanks again.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated