kpmedia

When, when!? I keep having to edit Blesta manually, and it really stinks.

Just update the ETA. Communication is all customers want. (But eventually, yes, you need to deliver.) I'd like to be kept abreast of new developments myself. It's why I even bother coming to the forum.

The "E" in ETA is "estimated". For business to say "I don't know" doesn't fly in the real world. They can estimate. ie Q1, Q2, Q3 or Q4 of 2016. You're just a forum mod, not one the Blesta devs. Perhaps let them answer.

Softaculous refuses to install Blesta unless the DNS for the FQDN (subdomain or domain) is already pointed at the server. So you can't dev it privately, then launch when ready. That's a problem. I've never seen this with any other installer, so I'm more likely to believe it's a Blesta issue, and not a Softaculous issue.

How hard is it to edit this theme to add custom menu items? Is it any different from the default theme in this regard? Does your theme "phone home" (as I'm no longer using themes that do this; too many security issues). Where can I see a live demo of this -- I'm not paying $50 based on images alone.

According to what I'm reading in that thread, not anymore: http://www.blesta.com/forums/index.php?/topic/1078-vqmod-for-blesta-now-available/?p=36147

From a business standpoint, that's not acceptable.

Cody claimed it was "not a bug". While that may be true from a purely coding stance, it's still a bug from a common sense stance.

Seems like an oxymoron to me. You: "Oh, you don't need a module? Okay, great. ... Use this module!" Me: "WTF?" Thanks for the info. It still doesn't make 100% sense, but I just won't worry about it. I'll mentally file this in the "WTF" file, along with what women are thinking, why people believe 9/11 is a hoax, etc.

This was a 100% new install. Clear caches does nothing. It's a bug.

Ever do this?

I'm not sure what you want a screenshot of. I did something like that years ago, but I don't remember when, or even what language (ASP? PHP?). When the code is being parsed, the plugin says "no you don't!" and replaces it. I vaguely remember it being vBulletin, back in 2009. Yeah, I think that's it. I took the basic function that was started, and edited it to do what was needed. Anyway, it's replaced on-the-fly with this other code, thanks to a plugin that acts first. That one plugin could be made to do everything I want! - What a better menu? Replace it! - Want to add a page? Replace code (to add it)! * - Want a better image? Replace it! * I needed a simple news page. I'm currently recycling "payment accounts" (useless for me) to make it. All it needs is fields to store the code in the db. You can add as many replacements as desired. All it does is seek out X and replace with Y. I remember that aspect of the replacement. But it's been so long that I don't remember how I did it. I wanted to start easy. A simple replacement just for this bit of code. Does this all make more sense?

I'm sure it seems like a basic question, but I've not found the answer. - You can't make a new package with out the "universal module". Why? - If you add a service for a client, one of the screens allows unchecking "Provision using the __ module". But unchecking it isn't doing anything that I can tell. If I hit BACK in the browser, it's now checked again. I assume this means it will be checked no matter what you do. I read this: https://docs.blesta.com/display/user/Universal+Module But I'm still having a hard time understanding why it NEEDED for basic adding of services and invoicing. I see the docs start out by saying "The Universal Module is the module to use when no other module will do." But why does it need one at all? The email aspect is especially confusing, and doesn't make any sense. I'd like a clearer explanation, please.

If I have a service ($10) that's prorated for 28 days, then it's $1.33 If I want to override that price -- let's say a 50% discount for the first month, as haggled via email -- I override is to $5 instead. If I override the price, now it shows $-0.67 Uh.... I owe them money.

Found a bug... If I add a client, and create a recurring invoice, then subscriptions do not work. Only one-time payment can be made. If I go through the hassle of making a module (what is that for, anyway?), then create a service, then add a client to the service, only then does it allow subscriptions. For a custom customer -- let's say somebody that hired you for 3 months of special coding -- you'd have to go through the nuisance of creating all this extra stuff. Furthermore, would it be visible on a front-end via the order form? It's supposed to be a "billing panel". At the base level, it should do at least that, and extra steps should not be needed.

Even if I add a recurring invoice, Paypal subscriptions are not working. It used to work, when I lasted test it in 3.4.3. This was the entire reason I bought Blesta.

I've already cloned en_us and made a new language. And I've already installed it in Blesta. But what about the plugin languages? Those are not changing. They appear to have nothing to do with Blesta's main language options. If the PLUGINS are supposed to also change, simply because the main language has changed, then I need to look at something else (cache?). However, given that it does give an error for a missing language, and still shows en_us, I'm somewhat doubting this is the case. EDIT It was a server cache issue. It appears that en_us is defaulted when another folder is not specified. I still think it was a mistake to not have a central language file (db driven to vBulletin). But at least the fallback is better than broken functionality. Thanks naja.

@naja, @jassdesi I'm pleased to here that I'm not alone here. I've been saying this for at least a year now. Blesta needs to rely less on plugins. The main selling point in 2013 was that "Blesta is more secure". Well, no, not really. Core might be, but plugins are not being audited. Plugins are being developed because core is somewhat feature-less compared to WHMCS (and Hostbill and ClientExec). And hosts will not be migrating to Blesta in this current state. It's simply not going to happen. Blesta has potential that it's not living up to. So hosts aren't buying it*. No use, no sales = Blesta fails, dies, and that's the end of that. I've been online a long time -- probably before some of you were even born. I'm NOT exaggerating, and have seen this story play out too many times. - The UI is important. Right now, the default UI is confusing as hell for customers. People are generally not that smart ("HELP!!! CANT FIND PAYMNT BUTTON!!!111"), and even I've been had by two UI quirks. The buttons and linking are horrible, and UX gets an "F" (maybe a D- if I'm generous). - The admin area is important. That menu is awful. You have to click and tap extra times (and wait for yet another page to load) to do what should be less cumbersome. It reminds me of those BS sites that say "10 ways to do X" and then expect you to click through 10+ pages to read their crappy list. - Features hosts need are simply not there, or not working well. That's just the blunt truth of the matter. At this point, I really don't care who does or does not agree with me. And I do feel as if the Blesta scene is dying off already. What few of us are left are still having conversations about the same things we were in 2014. Why does it take so long to fix simple things? (Seriously, a Paypal default button image? Really?) I'm trying to fix some issues myself, and I'll post my fixes for others. (And thanks to everybody that's helped me to date.) I can use Blesta for my minor not-hosting needs. But sadly, Hostbill, WHMCS and ClientExec are the only serious choices for hosts at the moment. I kept waiting and waiting and waiting, but it appears that I'm just waiting in vain. Blesta is stalled, with only minor improvements every 6 months. * It's actually very good for non-hosting needs (potentially), and is my main desired use.

I'd want to see it in action, but this does look like an improvement. Did you ever release the code on this, or are you planning to?

Yep, that's what I thought. Just wanted to make sure.

I'm guessing that this doesn't change the gateway's language to en_us to something else, but merely changes ... something else? The name of the plugin?

Is this just a right justify for language that are right-to-left?

/plugins/support_manager/language/en_us/ ^ This. I want to edit support_manager_tickets.php but do not want it to be overwritten by updates. My "fix" for language issues has been to make up a new one. So no more "en_us" (English, U.S.) for me. Nope, I'm using "en_tx" (English, Texan ). TX is not official, but its working for the main Blesta. Now the issue is the plugins and others that have their own language files. I think Blesta messed up here, and ALL languages should have been in the main language folder. (That's how vBulletin works, something I'm far more familiar with coding.) Where can the language be changed, so as not to be erased on update? Another idea would be to allow an exclusions file for updates. Granted, that means more coding to later allow less coding, but some of this software just was not planned out very well. It's all getting to be spaghetti code by duplicating functions everywhere. (It reminds me of too many WordPress themes that have plugins outside of "plugins".)

Found it: http://www.blesta.com/forums/index.php?/topic/2532-change-paypal-buttons/ That was a thread from a year ago, and nothing ever came of it. (This is why I'm getting feed up with Blesta.) All that's needed is a simple image change for the core, and it's done. As the Cody said, Paypal is fugly. Their not-buttons "buttons" are not needed. A good UI button is all that is needed. Hell, I'll make one, and even paste the code change here. All the Blesta devs have to do is copy/paste it to core, and problem solved. (Come on guys, what do you say?) My half-ass "fix" for now will be to clone the views folder. On update, I'll can rename/delete the new, and copy the clone to "default" restore it. But honestly, that's just more wasted time.

I'm not sure what you mean here. Do you mean: 1. clone it (got that part) 2. In paypal_payments_standard.php change class PaypalPaymentsStandard extends NonmerchantGateway { to something like class PaypalClone extends NonmerchantGateway { 3. And then change the process.pdt as per above for the image? Confirm this is it. Edit, nope not it still. Something is still missing. Blesta cannot find the clone. _______ I guess that's one way. It does seem a bit drastic, but I'm guessing the gateway won't need updates often, if ever. I'd still be interested in a "code swap" type plugin, if possible. I can see a lot of potential with it. I can see the code in my mind, in terms of usage. But I'm not sure how to start it. The menu is something I want to tackle on both frontend and backend. Right now, I'm hardcoding everything.