Leaderboard

Hello blestars A new Update for Support Manager Pro This version is only for Blesta 3.3 or above Added New: - All fixes and improvments from Support Manager Core in Blesta 3.3 - Added Red Badge to Client Area to show also the tickets Awaiting for Reply sended from Staff. - Services Tab in Admin Ticket Reply, that display all services from the client. (latter we will try to add an option to select a service from Staff and Client to associate in Ticket) Fixed: - Deleting all Replies from Tickets still display the Ticket in Satus and Badge count. - Bad encoding in latin characters. Improvment: - Renamed "Add to Delete" to "Move to Trash" - Renamed "Deleted" to "Trash" (because the tickets are not deleted are only in Trash, but you can still permenant delet them ) - Optimised code to support the new "events", and now is not needed to change core files. See first post how to install or upgrade Hope you like it

That may be true for some or even most people, but if you look around the forum you will find others who probably are startups who choose the registrar based on what is available. I don't see why Blesta needs to "Lose the ego". They are a business with limited resources and have to decide where to spend them to get the most return. Right now they are busy working on core features which are a lot more important than modules. Any business looking at Blesta can pay a developer to make a module, but if the core features are not there then that can stop potential users from switching.

Ok thanks. I believe the opensrs module is now available so I'll give that a go.

That might be why, I believe you need to use a module like Logicboxes / etc for the search query as it uses their API to check if it's available.

Blesta doesn't set a specific port when creating the server unless you provide that information (or it is already available from the package) when the service is created. Instead, Multicraft determines the next available port based off of your Multicraft settings and any other servers that are currently setup, in order to avoid duplicates. Perhaps your starting port number is not 25565 in Multicraft, or you have multiple Multicraft servers on that IP such that new servers get assigned a different port? I would need to see module log information to know more. Could you clarify? The log you've included looks correct--simply creating a server. There should also be several subsequent logs, and if you have an available dedicated IP setup under [settings] -> [Modules] -> [Multicraft] that was set for that service, you should also have a log entry regarding updating the server to use that dedicated IP. For example: http://domain.com/multicraft/api.php|updateServer a:3:{i:0;s:2:"78";i:1;a:2:{i:0;s:2:"ip";i:1;s:9:"daemon_id";}i:2;a:2:{i:0;s:13:"123.123.123.123";i:1;s:1:"1";}} That log shows the IP being set to 123.123.123.123 and the daemon ID set to 1. Search the page for ip and you should find that log entry indicating the dedicated IP was set. The last log in the list contains the information set for the server as given by Multicraft, which should contain the same IP. For example: http://domain.com/multicraft/api.php|getServer s:353:"{"success":true,"errors":[],"data":{"Server":{"memory":"256","start_memory":"0","port":"25580","id":"78","name":"Minecraft Server","ip":"123.123.123.123","dir":"server1","world":"","players":"10","jarfile":"","autostart":"1","default_level":"10","daemon_id":"1","announce_save":"1","kick_delay":"3000","suspended":"0","autosave":"1","jardir":"daemon"}}}";

The offline payment gateway is only intended to support Markdown text. See Markdown syntax Here's an example: # This is a heading This is a paragraph - List item 1 - List item 2 1. Number list 1 2. Number list 2 [Text to link](http://google.com/) Produces: <h1>This is a heading</h1> <p>This is a paragraph</p> <ul> <li>List item 1</li> <li>List item 2</li> </ul> <ol> <li>Number list 1</li> <li>Number list 2</li> </ol> <p><a href="http://google.com/">Text to link</a></p>

We are running Version 3.3.0, and Multicraft Module 1.2.0. We are already running the latest build, and it's a problem where the Dedicated IP won't be assigned itself. http://<REMOVED>|createServer a:4:{i:0;s:0:"";i:1;s:0:"";i:2;s:0:"";i:3;s:2:"20";} http://<REMOVED>|createServer s:46:"{"success":true,"errors":[],"data":{"id":"7"}}";

@Paul: My point of vew is better like this: Admin Side: a) In Services Widget, have an Multi Select (like in Tickets, mass operations), for what services you want create an earlier invoice (simple create one invoice with the selected multiple services), and then the cron will send by email the invoices to pay. Client Side: a) In Services Widget, have an Multi Select (like in Tickets, mass operations), for what services he wants to renew earlier, and then it will redirect to Payment Option to im to pay, (simple create one invoice with the multiple services selected), and then the cron will send by email the invoice to pay. In both ways, , only after the xx days (defined in backoffice to suspend), after the actuall renew date, blesta cron will auto suspend the services, and not before. @Jonathan: Dosent make sense select xx cicles, because cliente and admin side have an option to change the "Term" cicle, and in 14 years in hosting buisness it tells me that this is the eseast way to work both for Admins and Clientes P.S- Is just my opinion