Paul

I'm not sure I understand what you're asking. CORE-3573 has been completed for 4.10, which allows for searching the reference_id column for transactions, which contains the PayPal payer's email address. But it sounds like you want the ability to ban users based on PayPal account or IP address? That sounds like a different feature entirely. You can make an official request at https://requests.blesta.com

You may not have unpacked it correctly. Check that you don't have a /components/modules/namesilo/namesilo/ directory. The contents of the namesilo directory from the zip file should be in /components/module/namesilo/

500 errors are generally server-side and can happen for any number of reasons, the most common being incorrectly installed ioncube loaders. If the .htaccess file is missing, you should re-upload it. You might consider re-uploading Blesta entirely (after making a backup) to make sure no other files are missing. Check the logs ../logs_blesta/ defined under Settings > System > General to see if there are any errors being logged. Also ensure that your log files are all owned by the same user and have write permissions. Your cron should run as the same user as Apache. If you are executing your cron using wget, GET, lynx, etc as a web request then it should be, but this is not the preferred way to execute the cron.

I don't see a problem necessarily with your code, it's just checking if it's Saturday or Sunday (6 or 7), and not executing the code to generate invoices. Personally I would have made Sunday 1 and not Monday as Sunday is actually the first day of the week, but I digress. Maybe @Jono has something to add.

What version of Blesta did you do that with? Are you trying to prevent the generation of invoice, or only email delivery? You edited the /app/controllers/cron.php file? Can you provide a snipped from the file showing your change and a few lines above/below? Out of curiosity, why no weekends?

The error seems to indicate a CSV import, were you trying only to import your clients and no other data like services, invoices, etc? Here's the docs for the CSV importer https://docs.blesta.com/display/user/CSV Check your CSV file to make sure none of the required fields are missing for any of your clients.

I would guess that it works, but the best way to find out is to give it a try. If you need a trial key and already had one let me know via PM and I can get you one.

Looks like you figured it out before anyone had a chance to look into it. Glad to hear it's working now!

Do you see any reason we shouldn't search those fields in a transaction search? I know we added the reference_id after the search was originally written, but it's a field we should probably be searching.

Did you import into a fresh install of Blesta? It looks like some of the data being imported may be missing. Did any clients get imported?

We recommend using this version, it will be shipping with Blesta 4.10 https://github.com/blesta/module-namesilo

Welcome back! I'm not aware of any issues with the module, the official Logicboxes module works fine and we didn't make any changes to the core that should have broken 3rd party modules.

We do store the PayPal Payer email for the transaction now I believe, would a transaction search pull that up @Jono

Make sure you're editing /app/views/client/bootstrap/structure.pdt for the client area and front facing pages. If you've installed a custom template, then you may need to replace the part of the path including "bootstrap" with the name of your template. Also check that you are not entering the code in the middle of a conditional, which would only be displayed during certain conditions.

Version 4.9.0 is now available, please see the release announcement. Patching Blesta See Patching Blesta in the User Manual for instructions. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Migrating to Blesta See Migrating to Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.9.0. For older releases see all Change Logs.

Each order form is unique and packages cannot be ordered from multiple order forms at the same time. Most people only need a single order form, and add all of the Package Groups they want to sell through it. Most of your questions are vague. Yes you can access the database through the record component, see https://docs.blesta.com/display/dev/Database+Access There are routes for pages, see https://docs.blesta.com/display/user/Configuration+Files#ConfigurationFiles-routes.php

Blesta version 4.9.0-b2 (BETA 2) is now available. You can download it from right here (Client Area Login Required). Read the blog post announcement at https://www.blesta.com/2020/03/31/blesta-4.9-beta-released/ This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. Please report any bugs you find in the v4.9 beta bug forum. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.9.0. For older releases see all Change Logs.

Blesta version 4.9.0-b1 (BETA 1) is now available. You can download it from right here (Client Area Login Required). Read the blog post announcement at https://www.blesta.com/2020/03/31/blesta-4.9-beta-released/ This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. Please report any bugs you find in the v4.9 beta bug forum. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.9.0-b1. For older releases see all Change Logs.

Thanks for the update, glad to hear it's working!

To revert you'll need to undo all the things you did when installing BlestaCMS. From their docs https://cms.blesta.how/ If you have uninstalled the BlestaCMS plugin under Settings > Company > Plugins, you may also be able to re-upload a copy of the Blesta files to restore them to their original, essentially undoing your custom modifications for BlestaCMS. Backup your files + database first just in case. The re-upload the full version of Blesta that matches the version you are running. Don't delete anything, you want to make sure /config/blesta.php is not removed and remains in place. Then, install the portal plugin for Blesta if it's not installed under Settings > Company > Plugins.

Did you enter the full URL to the logo in the field? If you copy/paste that URL into your browser does the logo load? It's a good idea to use https:// for the logo, some browsers will not load unsecured content, and that could explain why it doesn't appear also.

Will this be an issue for everyone using DA? Should this be the recommended tag in the doucmentation?

You need to use Blesta to create your DirectAdmin hosting accounts. Blesta will provision them, no need to do it manually through DirectAdmin any longer. Here's the docs for DA https://docs.blesta.com/display/user/DirectAdmin If you are provisioning from Blesta and getting an error, check the module log under Tools > Logs. Click a record to expand it and show the raw input/output.

New tasks were created for the Affiliate system, so the old task was closed. Those tasks are currently private, but will be made public closer to release. The Affiliate system is in active development, and it is integrated with the Order Manager. It will be able to be enabled or disabled through a new core feature that allows individual plugin actions to be disabled or enabled. I hope that makes sense. New tasks (many) related to Affiliate, old task closed as a result. Affiliate system in development.

Also, you're missing a comma before your password rule. Try this ruleset: { "Domain":{ "valid":{ "rule":["matches", "/^[a-zA-Z0-9][a-zA-Z0-9-]{1,61}[a-zA-Z0-9]\.[a-zA-Z]{2,}$/i"], "message":"Domain must not be empty." } }, "username":{ "valid":{ "rule":["matches", "/^[a-z0-9\\$\\%\\^]{6,8}$/i"], "message":"Please enter a username using alphanumeric characters between 6 and 8 characters in length. You may also include number characters like 123." } }, "password":{ "valid":{ "rule":["matches", "/^[a-z0-9\\$\\%\\^]{8,20}$/i"], "message":"Please enter a password using alphanumeric characters between 8 and 20 characters in length. You may also include special characters like '$%^'." } } }