interfasys
-
Posts
249 -
Joined
-
Last visited
-
Days Won
3
Posts posted by interfasys
-
-
Search doesn't work when not logged in apparently...
But looking at James' response I see that he's interested in getting information from Blesta into an external Cachet installation, but I'd like Cachet to be a page within Blesta so that customers can use their login to have access to the information.
-
Cachet would be very useful to users and it's also easy to manage for admins
Github page
https://github.com/cachethq/Cachet
Features- List your services components
- Log incidents
- Markdown support for incident messages
- JSON API
- Translated into eleven languages
- Metrics
- Subscriber notifications via Email
- Two factor authentication, with Google Authenticator
To test out the demo, you may login to the Dashboard with the following:
- Username: test@test.com
- Password: test123
-
Nice. One thing which would be great is to be able to import all domains when adding a customer. There must be a way to create a link using the email address as ID or if not using some logicboxes ID.
-
Can't upgrade original with this one in 3.5
Module 'Logicboxes' does not exist. on line 29 in /components/modules/modules.php Printing Stack Trace: #0 /app/models/module_manager.php(908): Modules::create('logicboxes') #1 /app/models/module_manager.php(356): ModuleManager->loadModule('logicboxes') #2 /app/controllers/admin_company_modules.php(133): ModuleManager->upgrade('1') #3 /lib/dispatcher.php(111): AdminCompanyModules->upgrade() -
I would like to see this fixed as well so that I could switch over. I paid for my license a couple of years ago and still haven't been able to make the move. I don't know how to develop this but I could certainly test and provide feedback.
I'm on the same boat. I've been pushing for the change to happen for 2 years and it's always been pushed back. I wasn't even disappointed that nothing had made it into 3.5, because I stopped waiting. Domain management is bad and makes us look bad, but it's what we have and we just have to do more work behind the scenes to help advanced customers.
There are plenty of examples out there of what we need -> every big domain selling platforms which welcomes us as resellers (Enom, Logicboxes, OpenSRS, etc.. The only difference is that we're at one level above, pushing commands to different providers, depending on who we want to use to manage a specific extension.
-
A reputable developer can start working on a Netim module so that we can finally start selling and managing ccTLDs at reseller prices (forget Enom) and manage them from Blesta.
Before getting started, I want to see if anybody is interested in sharing the development cost.
If so, we would need to discuss copyright, distribution, etc.
Let me know ASAP.
-
Thanks for the clarification
-
I thought the OVH API was horrible and to be avoided or is this module poll about their hosting services only?
-
I don't think it should Paul mate, how can people add a card for future use or like me I have it stored on Blesta, but I only use it if needed, as I use the PayPal option for most invoices (minus Bitpay).
There is no need to add a card for future use if the service provider doesn't support that functionality.
In the case of Blesta, it does support it, so it makes sense to show that option, even if the customer doesn't want to use it.
-
We are using this one in the marketplace for creating descriptions for extensions - http://www.codingdrama.com/bootstrap-markdown/
It is dependent on Bootstrap, and the admin UI in Blesta is not bootstrap. But yes, it would be nice to use something similar in Blesta, and we have discussed it. If there are any libraries you can recommend, happy to check them out.
World class PHP markdown parser: http://parsedown.org/
-
Dynadot is actually worse when it comes to ccTLDs, but Hexonet must have one of the largest selection. There is no Blesta module though and it's expensive.
-
if you find extensions you want at internetbs.net there are very good at price, api, support. & Blesta module ever exist.
and yes NETIM seem very better than OVH (OVH: 5 year after, I still receive every month email from their system saying they will be deleting x inactive domains, when these domains was ever moved to an other registrar 5 years before, it's just creazy).
Not enough choice at internetbs, although it's gotten better since they've been bought.
Enom now has more ccTLDs, but it's usually overpriced for resellers, as in more expensive than buying retail elsewhere.
-
Good points, especially the ones about package migration. I'm almost certain that Blesta would not detect if an extension was to change package and that could lead to renewal issues.
That answers my question here: http://www.blesta.com/forums/index.php?/topic/3107-one-domain-package-per-extension-or-per-price/
but I really hope Blesta delivers an improved domain manager quickly as I'm not sure I want to manage hundreds of domain packages
-
I manage thousand of domains, and I would say, I tested OVH before doing this business and in my opinions OVH is very very bad for domains, at API or even from their interface you can not really do bulk update, and their desktop application bad.
Thanks for your feedback. I've heard similar things about their SOAP API before, but thought things had improved when they introduced their HTTP API. It turns out it's incomplete and doesn't seem to support domain registration...
That only leaves Netim as a viable, cheap option.
-
the advantage I found by creation of one package by each domain extension, is each domain extension can use a different registrar module, & can have different price.
So if later you change registrar or price, that's just more flexible
Correct me if I'm wrong, but if you create one package per price range per example, then if you ever need to change the price, you can simply untick a domain in one package and tick it in another, no?
For promotions you could create a new package with just that domain.
-
ovh is a good one ... i'm sure in the feature we will have one, as we have now a lot of blesta useres use the ovh service (server/domains/sms/vps/cloud ....)
Have you started working on this?
-
And the next week went...
-
I agree and was disappointed when I saw that the newly introduced knowledge base was not fully multi-language. Adding he proper calls to translated strings has to be embedded in the coding practice or it will get worse with every release.
The dev team needs to sit down with someone using the system in 2 languages or more to fully understand the depth of the problem.
- a.daniello and Blesta Addons
-
2
-
Lots of systems which feature markdown syntax have a preview system. It would be great if we could have a preview tab. That same tab could be used for HTML reviews as well.
-
License number or CLI only would work for us. It's only a problem in case of a botched upgrade imho, but still important as nobody wants any perp to be able to have access to that page while things are not working properly.
-
Current English only.
Thank you.
-
How many languages do you or plan to support?
-
Blesta is now part of Installatron!
- ModulesBakery and Paul
-
2
-
- I cannot and don't want to use unofficial PHP classes made by third parties, i have created my own class for API integration.
It's obviously your business decision, but an open source library published on Github offers several advantages over an encoded file:
- Audited by at least one 3rd party for code quality and security
- Adaptable to one's needs
- Transparency
- Collaboration
But I think this argument will always exist. Some people don't want to or can't use encoded files while other don't care as long as it gets the job done.
Sad State Of Domain Management And Blesta
in The Lounge
Posted
Domain management in Blesta works if your customers have one domain they've bought at the same time as their hosting or if they've transferred the few they own and don't care about maintaining them (leaving that ICANN responsibility to you). It fails when you have a dozen+, spread across different registrars and if you're selling more exotic domain names (with the registration restrictions).
The biggest problem though is the lack of self-service option on the client side. It should be as good as what Enom or Logicboxes has to offer. Customers should be in control of their domains (contacts, DNSSEC, EPP, privacy protection, trustee service, etc.). Blesta should just sit one level above registrars, offering the huge benefit for customers of having only one system to use to manage all their domains.