clusterx

I would like to hide the frontend menu including menu background completely in the classic template and only show it to logged-in users. Can I use this function in the main-header.php for this: <?php if($login_check): ?> and from which line (from > to) should it be placed?

Are there any other data (e.g. login details, API login details, module logins, credit card data, etc.) that are stored on external WISECP servers apart from the admin folder name?

WHMCS Version was missed, sorry 😉 WHMCS 7.10.3 WISECP - latest stable

PHP 7.4 (fpm) Debian 10 I am currently trying to import data from whmcs (Test import) but it always sticks on: Orders > Processing...... 2 files are generated in the tmp folder /temp eb78897b08c58bb4ad7b4318ad3c6dc4-data.php eb78897b08c58bb4ad7b4318ad3c6dc4-result-collation.php but nothing happens after that, it just shows Orders > Processing...... and there are no further actions in the tmp folder I use the recommended settings for php and mysql wisecp error log: MESSAGE Trying to access array offset on value of type null

Is there already a server overview in WISECP where you can log into the ControlPanel directly as Admin? I don't mean a login into the customer accounts, but the reseller account of the server to quickly make administrative changes or install new certificates etc.

it seems this is caused by the menu links to the demo - using http instead of https 😉

Hi Onur, thanks for reply! I have tried w/ allow all cookies but it still shows the red bar "Invalid CSRF Token" maybe you should check this login issue with latest chrome browser - I use Chrome Version 93.0.4577.82 on Arch Linux. I think the problem could also occur w/ customer login or a customer order. only Firefox let me in 😉

if I use "block third party cookies" on google chrome I cannot log into the demo admin area... it shows: Invalid CSRF Token it still works with firefox, with chrome since latest updates > Invalid CSRF Token

What happens when the wisecp license server fails (network outage or maintenance) are the wisecp installations (front & backend) still accessible and working during a wisecp server outage? My question is based on wisecp clientarea functions because the client admin folder name & other stuff are stored encrypted on the wisecp servers ...

I have already deactivated the SMS module but the SMS service is still present everywhere (front and backend) ... any suggestions?

is it possible to create a child theme for the Classic theme or can I save and customize the Classic theme under a different name? e.g. replace Classic in all files of /templates/website/copyofclassic find /mypathto/wisecp/templates/website/copyofclassic -type f -exec sed -i 's|Classic|copyofclassic|g' {} \;

If a customer already has a domain name in the cart (added via domain search) and then he click the link to the hosting packages (dteails) the domain name already in cart is not taken into account, so the customer have to remove first the domain from cart and start from scratch, select hosting > then domain name ... after hosting selection there should be a possibility if there is already a domain name in cart to select it to proceed with the order

regarding the base64 stuff .... do you think a hook file for the phpmailer is possible, or in which file (e-mail headers) can this be added? https://www.labnol.org/code/19840-base64-encoded-email

ok I got it, I missed to add the [mysqld] section header 😀 thank you Onur!

thank you! changing the admin folder name worked now, it seems that only lower case letters are accepted here when I do a check in mysql the following is displayed mysql -u root -p -e "SHOW VARIABLES LIKE 'sql_mode';" +---------------+-------------------------------------------------------------------------------------------+ | Variable_name | Value | +---------------+-------------------------------------------------------------------------------------------+ | sql_mode | STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION | +---------------+-------------------------------------------------------------------------------------------+ It seems the strict mode is already off, but the health status shows a message to turn it of in /etc/mysql/my.cnf