Leaderboard

I read this as "I'm sitting in the emergency room with my wife at the moment. Two 9mm shots to the kidney, and a bladder infection." For a second there, I thought you got shot. And then I wondered why you would be on the forums at a time like this.

Just an update on the plugin I'm working on. The admin section seems to be working fine now. Not making it too fancy or complex. Simple categories with articles in them. I'll modify this post with updated information when I finish a release.

That's a good point. One very nice thing that I have seen over the past year as I've watched Blesta, is that Blesta management is very open and honest. It's what initially convinced me to purchase a license even before v3 was finished, and evangelize about Blesta to other people. And it's what makes me impatient and want to move to Blesta now, even though it doesn't have the necessary functionality just yet for my business. So while I'm reasonably confident they'll eventually move to a true marketplace as I've described, and remove the "extra" stuff from the core product into individual saleable modules... I think they will be ethical and upfront about it, and they will not screw existing license holders. ie: Anyone who has an existing license would be entitled to a free license of every individual module that is removed from the core, including updates. I can't see Paul et al doing it any other way.

I hear your concerns and they will too, electric. But I think you're overthinking their intentions with free modules. You're worried about a monopoly so to speak even though you're not directly saying it. But that's not consistent with them giving away 93% of their code and implementing an open marketplace. This discussion could go on forever. But the fact that we have such a diverse opinion and needs to me proves that there will be plenty of opportunity for 3rd party modules. Blesta can't keep up with the development of several companies on several products. I just don't see it. Don't worry so much. Take it day by day, and if you're worried about Blesta charging for modules in the future then just expect it. The worst that'll happen is you'll have been right.

I'm against this completely. If I update a ticket I want it going out immediately because I work in a mission critical environment where seconds count. As far as editing I'm going with Paul on this one... the email would be sent out via email so even if you edited the ticket that would be inconsistent. Unless an "Edit" email want out to them but then why not just update the ticket again with the correction. The ticketing system is nothing other an a fancy email client. I treat them like emails because you can't edit emails either. There's my input.

Yea but you're comparing apples and oranges. Blesta has been for a while and a lot longer than Hostbill unless I'm mistaken? But if you look at Blesta's track record I think you'll find it very consistent, careful, and complete. Unlike Hostbill who has been sporadic since day one. So I don't think CubicWebs is trying to push his opinion on you but rather instill some confidence from their core users that they haven't really displayed that kind of behavior. As far as you wanting an indefinite price guarantee I want you to show me what company would do or say that? If they have any pricing model changes they will let you know well in the advance. Unlike HostBill who is focused on selling modules and not doing much with the billing system, Blesta is billing system focused and their modules are a part of it's evolution. Then there are 3rd party modules on the marketplace. Of course these things will need some maturity as v3 just came out. But I'm personally glad that I'm ahead of the curve as I like the simplicity at the moment. It's made transitioning very easy for many.

There will be an official KB, and depending on when we do it it will either start out simple and receive a subsequent update to add more tight integration, or be released with tight integration to begin with.

Find the user_id in the staff table, then look up that user_id in the users table. The most common mistake for resetting passwords has been users entering their email address instead of their username when requesting a password reset. Be sure to use your username and you should receive the reset at the email address as listed in the users table. In the event that you still don't receive the reset message, check the log_email table for the message. If it's in there you can copy/paste the URL out of the message into your browser.

thought it was a slightly unique idea.. better then hetzner's "auctions" at least the user gets a slight say to make it cheaper then to make it more expensive

Just worked it out i think.. here is what i have put it too... if it has the option for monthly, quaterly or yearly. (as far as i can tell because my product id for '1' is only a single item for 1 month) it stays the number. if it has any payment options it has id+1. i've just put that in my script to see what happened and 3 of them have worked so far.. by all means michael, check it out (buydedi.com) let me know what you think.. down the bottom "haggle"

Yeah i'm fine Just customizing Blesta on my days off having a ball lol Funny thing is it's showing my accounts total in WHM on the "Manage Server" page correctly so it is connecting ok i think. cPanels spatt it's dummy out over some setting or other... lol

I stumbled on "total", "incredible" and a few other words, so I guess I'm a "kid".

Hi Bob, This is corrected in 3.0.3 I believe, and a patch should be out next week. When a user registers, they will be directed to the client Dashboard.

Contact logins with ACL permissions is actually on our list, CORE-627 and is tentatively schedule for 3.2. We will considered sponsored development for core features, however we will only do those if we already agree that we want to include it. Same really goes for extensions too. We try to prioritize development based on demand, and in all honesty someone willing to part with some cash says a lot about how serious they are about throwing their support behind something. It's possible to have 100 votes for a feature that nobody will really even use but sounds cool. We would rather build the feature that 10 people would actually use than the one 100 people voted for but wont use.

Says a little bit about how the brain reads and processes words. Similarly, Did aonnye ncitoe how aanizmg Btelsa's new safwtore is? I cnduo’t bvleiee taht I culod aulaclty uesdtannrd waht I was rdnaieg. Unisg the icndeblire pweor of the hmuan mnid, it dseno’t mttaer in waht oderr the lterets in a wrod are, the olny irpoamtnt tihng is taht the frsit and lsat ltteer be in the rhgit pclae. The rset can be a taotl mses and you can sitll raed it whoutit a pboerlm. Tihs is bucseae the huamn mnid deos not raed ervey ltteer by istlef, but the wrod as a wlohe.

It sounds like there may be 2 or 3 things going on here. The first error that says to use GET finally clicked with me. We had a similar issue in v2 a couple years ago because the live and test APIs behave differently. This is why some of you experienced a problem, while we couldn't duplicate it in our test environment. I believe the solution to this problem is the following: Update /components/modules/logicboxes/apis/commands/logicboxes_customers.php (line 177) return $this->api->submit("customers/search", $vars); change to: return $this->api->submit("customers/search", $vars, "GET"); Then try creating another service and let me know what happens. You unchecked the "Use Module" checkbox when you added the service? And it still attempted to add it using the module? That doesn't sound right.

CORE-747, tentatively scheduled for 3.3.

That's what it's all about!

And so it begins: the great Blesta community module drive.