cluster

can I migrate from WHMCS if the date format is different? or should I have to use exactly the same date format as set in WHMCS? WHMCS > Global Date Format DD/MM/YYYY BLESTA > Date Format d.m.Y Date Time Format d. M. Y H:m:s

Is there any chance to change the Blesta internal captcha to show only capital letters? The upper and lower case is sometimes difficult to recognize and it takes a lot of attempts.

Is there a Blesta module & recommended provider which allows processing of DNS zones by the customers?

any news for the planned Keyhelp module? https://dev.blesta.com/browse/CORE-3658 I would like to switch to Keyhelp but I'm not able to create this module by myself from scratch.

It will take me a few months to finish some special modules, therefore I can wait for the official Blesta 5.1 release ... So I'm thinking about starting w/ 5.1 beta to set up and prepare everything. Is it possible to upgrade from a beta version to an official release afterwards? Thank you for the great work!

I think I will choose Blesta and migrate from whmcs soon ? one more question about the invoice emails ... the shared invoices function what does it mean exactly? Is this function safe (using an one-time individual string link) ... with "safe" I mean if someone pays via the link is then the payer automatically logged into the customer account after the payment and has access? Would a css attack be possible via GET variables to access the client area from a payment link? I would like to use the payment link function for invoice emails if it's safe and the customer accounts cannot be compromised via payment links.

is the following possible with Blesta (e.g. hooks, plugins etc.) 1. captcha integration into login froms 2. Login notification for customers via email (notification for a successful login via email to the customer, incl. date, time IP address 3. max login attempts - blocking after x fail logins 4. blesta installation in subfolder /clients without blesta rewrite to a second /clients Folder - for now it shows /clients/clients/... when blesta was not installed into webroot thank you guys!

thanks, this plugin is already on my list ... I thought I have to wait until the updates or does it work with Blesta 5.x?

how can the lang string in the url be rewritten to point to a virtual folder and exclude the admin folder from rewrite? https://www.mydomain.tld/?lang=en_us -> https://www.mydomain.tld/en/ https://www.mydomain.tld/?lang=fr_fr -> https://www.mydomain.tld/fr/ https://www.mydomain.tld/?lang=de_de -> https://www.mydomain.tld/de/ I've tried this but it doesn't work RewriteRule ^en/(.*) /?lang=en_us/$1 [NC,L,QSA] RewriteRule ^fr/(.*) /?lang=fr_fr/$1 [NC,L,QSA] RewriteRule ^de/(.*) /?lang=de_de/$1 [NC,L,QSA] also following doesn't work # Force HTTPS RewriteCond %{HTTPS} !=on RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [R=307,NE,L] RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ index.php RewriteCond %{REQUEST_URI} ^(.*)/install.php$ RewriteRule install.php %1/install/ [R=301,L] RewriteCond %{QUERY_STRING} lang=en_us RewriteCond %{QUERY_STRING} lang=de_de RewriteCond %{QUERY_STRING} lang=fr_fr # exclude all requests starting with /admin/ RewriteCond %{REQUEST_URI} !^/admin/.*$ RewriteRule ^(.*) /en/$1? [L,R=301] RewriteRule ^(.*) /fr/$1? [L,R=301] RewriteRule ^(.*) /de/$1? [L,R=301]

ok i have found the "lang" string which works for all languages incl. plugins, order page etc. https://docs.blesta.com/display/user/Order+System#OrderSystem-LinkingtoanOrderFormtoIncludeaSpecificLanguage https://www.mydomain.tld/?lang=en_us https://www.mydomain.tld/?lang=fr_fr https://www.mydomain.tld/?lang=de_de

I will try to explain better ... the language switcher does not change the URL which cause penalizing by google ranking due to "duplicate content w/ the same URL" so the point here is to solve an SEO problem (duplicate content) the URL should look like this after switch to another language: default language: https://www.mydomain.tld/ FR should be: https://www.mydomain.tld/fr/ NL should be: https://www.mydomain.tld/nl/ or https://www.mydomain.tld/fr/plugin/support_manager/knowledgebase/ https://www.mydomain.tld/nl/plugin/support_manager/knowledgebase/ that would be feasible via a mod_rewrite rule but only if the language switcher shows the string, i.e. changing the language with a GET string ... is there a possibility to use a function in structure.pdt that adds an iso code (fr) to the redirect_uri? for example ... if language french was selected <input type="hidden" name="redirect_uri" value="/fr/" /> <input type="hidden" name="redirect_uri" value="/fr/plugin/support_manager/knowledgebase/" /> the BlestaCMS plugin is working properly it appends the iso code of the language to the url but Blesta always shows the default URL after switching the language.

I have been using a multilingual whmcs installation (4 languages) for about 10 years, how can I integrate the languages into the Blesta frontend? Do I need to buy the Besta CMS for this or how can I integrate a language switcher in the Blesta frontend? ### edit ### oh, sorry for my impatience ? it seems to work with the BlestaCMS when I add the languages there ... I will pay more attention on it so I can get it work for my needs ### edit ### not really ... it works for own content pages only

yes exactly, I'm looking for the string or a function to trigger that

Is there really no way to switch languages from frontend?

is there any way to change the language via GET and POST requests from outside and what should the strings look like?

do you also have such slow connection and outages today w/ domain names using cloudflare NS as well blesta, whmcs and also the status page of cloudflare itself is building up extremely slowly here in europe? https://www.cloudflarestatus.com/ however ... I need some suggestions to solve a problem with weebly (whmcs market place) ... I have several weebly customers, is there a solution to integrate weebly into blesta somehow or how did you solve this issue?

great, thank you! maybe the base64 part works w/ a few changes in /components/email/email.php e.g. https://www.labnol.org/code/19840-base64-encoded-email also, it would be a little more safe when login details are send as base64 encrypted

I would like to switch from whmcs to Blesta, some time ago we got problems sending emails out to Gmail or Hotmail (despite a good reputation system emails went to the client spam folder) due to the login details usually contain many links, after they have implemented Base64 encoded emails it worked. Also with bulk e-mails e.g. maintenance notification we had issues due to gmail, hotmail, yahoo rate limits, therefore it would be nice if there is a function which delays email delivery e.g. 20 e-mails per minute. For a billing system it's important to be able to send base64 encoded and limited per minute for proper delivery of important emails and avoid blacklistings.

can Blesta send Base64 encoded Email or can it be activated somehow?

I would like to switch from whmcs to blesta & do a test migration before starting the customization stuff ... Is it enough to keep the cronjob inactive to prevent e-mails from being sent to migrated customers?