Jump to content

Paul

Blesta Developers
  • Posts

    6,687
  • Joined

  • Last visited

  • Days Won

    839

Everything posted by Paul

  1. You can create a configurable option for daemon_id and list multiple daemon ID's in there, separated by a comma. People use this for adding an option during checkout for like "Location", where say Los Angeles is a location, but multiple different Daemon IDs are associated with it. Then, the Daemon ID with the most available resources is used to provision the new server. See http://docs.blesta.com/display/user/Multicraft#Multicraft-ConfigurableOptionsOverview Do you think this would solve it? Maybe I misunderstand the issue.
  2. Do you have multiple Multicraft master servers?
  3. It's a separate system. Our implementation will be fairly basic compared to 3rd party Affiliate systems live iDev. If you use iDev, you probably wouldn't want to user ours, and the data won't be shared between the two.
  4. You change any files? I would recommend re-uploading all original files for the exact same version. A white page usually indicates an error, enabling error reporting in /config/blesta.php should show something, if not it may be suppressed or there may be a separate issue. Check your web server logs, is it showing anything other than a 200 response when you load that page?
  5. Try cancelling them under the clients profile via the Manage link. Then select Cancel in the Actions drop down. Uncheck the use module option if you don't want it to make an API call to kill the service outside of Blesta.
  6. Normally the token would be stored in Google Authenticator as your username. So, if your username is "John" for example, then it should be listed that way here. To set it up without scanning the QR code, please see http://docs.blesta.com/display/user/Enabling+Two-Factor Google requires the key to be in hexadecimal format, and that page references a utility for converting it.
  7. Well, thank you very much! That is odd, I'd need more information, such as the URL you're getting a 404 error at to even guess what may be happening. But if its a result of installing the plugin, then Mike is right -- try contacting iDev and see what they say. You may have stumbled on a bug in their plugin. That's great to hear! We recommend personally thanking iDevAffiliate if you use them for the Blesta plugin.
  8. Paul

    E-Mail Pipings

    Email has to come into the same server you're running Blesta on. That means you need to have a mail server running on that server. The mail server would be configured to pipe email to Blesta for those addresses. This is set up differently depending on the system and whether you're using a control panel. Most panels like cPanel, Plesk, Interworx make it easy to set up the piping. If you haven't already, take a look at http://docs.blesta.com/display/user/Support+Manager#SupportManager-email-pipingEmailPiping It describes how you might configure your server manually. If you have a panel though, you should use that instead.
  9. I created this task to address this - CORE-1593 In the meantime, I suggest setting up a forwarder for each action, and have the actions go to the forwarders. For example, service-add@, service-edit@, service-suspend@ This will allow you to indentify them until a tag can be added to the template.
  10. Ah, there should probably be some better documentation on this. Have you tried adding the {% debug %} tag to the email notification for the Universal Module Product? It should contain the action, and if it doesn't we'll need to correct that. I'll see if I can take a deeper look at it in a little bit. Right now someone in the building must be spraying perfume in the vents because I can taste it.
  11. I just came across this today - http://blog.idevaffiliate.com/affiliate-tracking-for-blesta-new-plugin/
  12. Have you looked at notifications? http://docs.blesta.com/display/user/Universal+Module#UniversalModule-Notifications This would allow you to be notified, by putting in your email, or URL to a separate system when an action occurs on the service.
  13. Your example highlights a problem I have seen myself. The "solution" thus far has been to create a separate account for the client that does not have auto debit set up for manual invoices they wish to pay by check. So, a way to tag or categorize services and manual invoices to omit them from auto debit would be very nice. Perhaps an option that can be enabled on an invoice to omit it from auto-debit. A similar option could be added to a service or recurring invoice to set this flag on invoice creation. Then, at anytime the option could be added or removed from any specific invoice.
  14. Thanks for the kind words and glad we could help!
  15. Great! If you want to write a how to guide that would be fantastic. I'd say, post in on the forums here in a new thread and we'll link to it from the documentation.
  16. Thanks for the update, glad it's working now!
  17. Hey, welcome! Does your .htaccess file exist - are you using mod_rewrite for pretty URL's? If you can see index.php in the URL anywhere, then you aren't and you may need to prepend it to the path to the order form. If you are, then I wonder if you have mod_security or anything running that may be blocking requests to that resource.
  18. Please see CORE-1589. Open to suggestions and comments if you feel the feature should work differently than described.
  19. Ok, pretty straight forward. So, what if we allow any staff assigned to the department to send a ticket to the trash bin, and then made a setting available to each staff so they can access and empty the trash bin? (This would probably apply to any/all tickets in the trash that belonged to departments for which they had access.) What does everyone think?
  20. How would you suggest we implement it? I don't think we would want to allow any staff to delete tickets, maybe a staff setting for that? If you have any suggestions based on Kayako's implementation, may be worth exploring those.
  21. We appreciate your feedback @snake and best of luck.
  22. If it's trying to provision and that is where it's failing, check the module log under Tools > Logs > Module Log. The cron provisions paid pending services, and on average it works out to 2.5 minutes to wait.
  23. Tell your friends! It would have no impact on the time/speed at which things are accomplished. Blesta uses its own internal scheduling, and the most frequently anything will run is 5 minutes. There are hacks to get around this, but we don't recommend it. A configurable option, or better yet the order form option "Require Agreement to Terms of Service", where you could include any other EULA's. You can select the directory from the Package, see http://docs.blesta.com/display/user/Multicraft?preview=/3833872/3899418/module-options.png "Look for JARs in the following directory", if that helps? Tyson may be more helpful on this one.
  24. Paul

    Mod_Rewrite Issue

    I've confirmed that it's in Blesta 3.4.2 from https://account.blesta.com/client/plugin/download_manager/client_main/download/61/blesta-3.4.2.zip /blesta/.htaccess Here's the content: ######################################################## # package: minPHP # filename: .htaccess ######################################################## <Files ~ "\.(pdt)$"> order deny,allow deny from all </Files> # Protect against Clickjacking #Header append X-Frame-Options "SAMEORIGIN" RewriteEngine on # 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] You can uncomment #Header append X-Frame-Options "SAMEORIGIN" to protect against click jacking, and the 2 lines under # Force HTTPS to force an https:// connection
  25. Mike, I think the test may be flawed. nxs_cURLTest("https://account.blesta.com/", "HTTPS to Blesta", "Blesta Servers"); The third parameter is "Blesta Servers" that's the text that the test is looking for in the page to confirm it was able to fetch the page. Change this to "Client Portal", and see if it comes back with a success. Did the IP, domain, or install path change? If you have multiple web servers behind a load balancer or something, then that is likely the cause. We need the IP for each of those servers.
×
×
  • Create New...