Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strict Standards: Only variables should be passed by reference in namecheapssl.php on line 2749 #23

Open
kochen opened this issue Jul 23, 2014 · 10 comments

Comments

@kochen
Copy link

kochen commented Jul 23, 2014

here is a patch: https://gist.github.com/kochen/82604351540990695f64

@kochen
Copy link
Author

kochen commented Jul 23, 2014

be sure to fix the same issue with the same code solution in line 2783 as well.

@kochen
Copy link
Author

kochen commented Jul 24, 2014

this issue happens also on the new V1.6.0 update form a few minutes ago:
Strict Standards: Only variables should be passed by reference in modules/addons/namecheap_ssl/namecheap_ssl.php on line 269

@kochen
Copy link
Author

kochen commented Jul 24, 2014

and on frontend (login as client):
Strict Standards: Only variables should be passed by reference in modules/servers/namecheapssl/namecheapapi.php on line 404

@kochen
Copy link
Author

kochen commented Jul 24, 2014

@vladkNC
Copy link

vladkNC commented Jul 24, 2014

Hello Kochen,

We've started performing parial refactoring of code for it to match strict standarts, but due to high amount of more prioritable changes that should have been made (fixes of issues blocking functionality, Heartbleed-related issues) we were not able to complete refactoring. It will be completed in next versions.

In order to get rid of such warnings please uncheck 'Display Errors' box in 'Setup' - 'General Settings' in WHMCS admin area:
http://www.evernote.com/shard/s358/sh/49477bb2-9f3f-489e-8ba7-57205e98d629/60dca29c2570355168249567f28642a7

@kochen
Copy link
Author

kochen commented Jul 24, 2014

I know how to disable the errors, that is not the point.
we are talking about 4-5 lines of code, which I actually provided the changes needed in a patch to fix the issue (just split the calls).
I see no reason to not fix it...

@vladkNC
Copy link

vladkNC commented Jul 24, 2014

I will discuss this with our developer, if this will not take much time - we will release an update.

@kochen
Copy link
Author

kochen commented Jul 24, 2014

it took me a few seconds.
and like I said I already provided the patch, so just apply it, it'll take even less time...

@vladkNC
Copy link

vladkNC commented Jul 24, 2014

Kochen,

I still need to doublecheck it with developer. He will be in the office within next few hours to check the changes provided by you.

Before releasing anything (even such minor things) we need to get through certain procedure of QA (even if it is just formal).

Thank you for your updates, I will return to you as soon as I have a conversation with dev.

@vladkNC
Copy link

vladkNC commented Jul 25, 2014

Kochen,

Thank you again for your cooperation.

We have added your changes to version 1.6.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants