EidolonHost

There's always ModulesBakery. They charge reasonable development prices. I'm sure they'd be happy to develop an eNom module for you if you ask them to. Or better yet, why not crowd-source the cost of the module development with ModulesBakery?

Hi, Something that I'm curious about — there is a step where you confirm the selection of the product you were planning on ordering. This confused me for a moment when I was going through the ordering process, testing the process to ensure that it flowed through just fine. Select product -> confirm product choice -> configure product -> summary of product -> pay bill. Shouldn't it be: Select product -> configure product -> summary of product -> pay bill ? And if so, what would be needed to achieve eliminating that unnecessary step? I mean, I know you can link directly to the product configuration order page from your main website's products pages... but I'm talking about when you go to the billing system directly and order a product, skipping the main website entirely. I think it's an unnecessary and confusing step since you're selecting the product. The product configuration page even states what product you're configuring. Isn't that enough? I posted it here because I don't think it fits Feature Request.

I've made it all work... except for that last suggestion you made, LicenseCart. I just can't seem to make it work no matter what I try. Also, I figured out how to change the blue bar colorings. Those're controlled by .panel-blesta > .panel-heading { color: #fff; border-bottom: none; background: #0075b2; background: -webkit-gradient(linear, 0 0, 0 bottom, from(#6fb1d4), to(#0075b2)); background: -webkit-linear-gradient(#6fb1d4, #0075b2); background: -moz-linear-gradient(#6fb1d4, #0075b2); background: -ms-linear-gradient(#6fb1d4, #0075b2); background: -o-linear-gradient(#6fb1d4, #0075b2); background: linear-gradient(#6fb1d4, #0075b2); -pie-background: linear-gradient(#6fb1d4, #0075b2); position: relative; behavior: url(../javascript/PIE.htc); } However... I can't seem to make the changes take. I see it take in the browser when I modify it using dev tools... but making it take in the CSS... it doesn't seem to be taking and seems to be overridden somewhere else. Paul, any ideas?

Oooh. You mean the other portions of your tutorial. Gotcha. I will be messing with this, yes. I plan on doing that when I head back home for the night and work on the dev server hosted there.

What do you mean by that? Specifically, the recommendation you're making. I'm not sure if you mean to move the Test client portion bit as you can see in the screenshot to the top, as in the bar where the logo and the services are?

If you're concerned about control and the like, why not use GitList?

Balls, so it was! Dropping in the JS at the head as suggested in your tutorial article fixed it. One more issue. It seems the drop-downs for the menus in the client dashboard isn't quite working as it should. The v carets are present but do not work when pressed. Also, need to move the client's name somewhat to the left along the nav-bar in the dashboard... as well as matching the color of those bars to the nav bars. I'll post a screenshot shortly and this can be easily seen. I'll figure it out soon enough. But boy, I made quick progress. I'll have to make sure to diff the differences between each new theme update and update accordingly... Edit: I attached the image... seems it didn't take. Uploaded to our server. Here it is:

I mean the login/register button that you normally get when you go through the ordering of a specific product in Blesta. You know, the one where it asks you to register and/or log-in to your existing account if you have one? It works fine in the Bootstrap client template but not in the EidolonHost template. I'm thinking I need to use Github to view the differences... I find it's much more easier that way, for me personally... But I digress. Basically though, this is all CSS, no? And well, some obviously Blesta-specific code to enable stuff like you want to?

That's already in my structure.pdt. This was the guide you pointed me to and it handily helped me resolve the other issues I mentioned here. Oh... a refresh showed that this was already taken care of and that I hadn't refreshed after I uploaded a fresh copy. Hurpadurp... I shoulda CTRL+F5'd. Still working on integrating the other stuff I need integrated. I think that's basically it. Also, I just noticed there isn't a register/log-in button/area in the order form. How does one include this in the order form?

So, this is mostly my fault for not getting into touch with @LicenseCart for the theme integration I had them do for us. So far, I've managed to fix the KB search fields issue, added Return to Staff portal link to the client dashboard... the only stuff I need to work on is the client dashboard itself. Right now I need to work on integrating the Services section, Invoices and Transactions sections that you'd normally see in the Bootstrap theme. How would one do this? I'm looking at the CSS/source of the output of structure.pdt for both and I'm not... well, understanding how this works. From what I see of the differences between the LC-made theme and the bootstrap themes, this seems to be mostly CSS-issues. That is, it seems that if I want to import these things, I simply only need to call the specific CSS files for say, InterWorx, Namecheap and the like, correct? I'm not a designer so I'm just glad most of the work was done for me... now it's just adding the relevant stuff into the client dashboard. Oh, and fixing the positioning of the client's name. I'll have that figured out sooner or later, I'm sure. Huh, looks like I fixed more than one issue by removing my custom theme's login stuff with the fillable boxes... I'm glad I hit upon that solution. Sidenote: How does one insert the Return to Staff portal link in the client dashboard? Is that in the structure.pdt? Or... what?

30, to 2400. And it was. Or rather, it seemed the server was fine, at least up until I went to try sending the e-mail out. Then it had gone away. I'm not entirely sure what happened for it to go away... but this seems to have fixed the issue.

Looks like raising the timeout fixed the issue. Bah. I looked at different results on Google and it wasn't entirely always clear what you should do... but include "Blesta" as a modified search result, boom, you get succinct answers.

So, New install and all. I recently started setting it all up again on a new server. Fresh database with one customer in it. Fortunately, I was able to shove through the payment receipt to the billing system before it died off again. However... this keeps happening every time I try sending a client e-mail. Specifically, Oh noes! SQLSTATE[HY000]: General error: 2006 MySQL server has gone away on line 124 in /home/user/web/domain.com/public_html/billing/lib/model.php Printing Stack Trace: #0 /home/user/web/domain.com/public_html/billing/lib/model.php(124): PDOStatement->execute(Array) #1 /home/user/web/domain.com/public_html/billing/components/record/record.php(669): Model->query('SELECT COUNT(*)...', Array) #2 /home/user/web/domain.com/public_html/billing/components/record/record.php(760): Record->fetch() #3 /home/user/web/domain.com/public_html/billing/app/app_model.php(0): Record->numResults() #4 [internal function]: AppModel->validateExists('1', 'id', 'companies') #5 /home/user/web/domain.com/public_html/billing/components/input/input.php(478): call_user_func_array(Array, Array) #6 /home/user/web/domain.com/public_html/billing/components/input/input.php(317): Input->validateRule('company_id', Array, '1', 'company_id') #7 /home/user/web/domain.com/public_html/billing/app/models/logs.php(91): Input->validates(Array) #8 /home/user/web/domain.com/public_html/billing/components/email/email.php(281): Logs->addEmail(Array) #9 /home/user/web/domain.com/public_html/billing/components/email/email.php(244): Email->log(Array) #10 /home/user/web/domain.com/public_html/billing/app/models/emails.php(755): Email->send() #11 /home/user/web/domain.com/public_html/billing/app/models/emails.php(638): Emails->sendEmail(Object(stdClass)) #12 /home/user/web/domain.com/public_html/billing/app/controllers/admin_clients.php(1355): Emails->sendCustom('sales@eidolonho...', 'Sales', '...', 'New Service Act...', Array, NULL, NULL, NULL, NULL, Array) #13 /home/user/web/domain.com/public_html/billing/lib/dispatcher.php(111): AdminClients->email() #14 /home/user/web/domain.com/public_html/billing/index.php(21): Dispatcher::dispatch('/billing/admin/...') #15 {main} How do resolve? Google has billions of different results and I hate working with SQL. Ah, I shoulda done a search including Blesta. Will post back results shortly... *mumbles* Let's see if raising the wait timeout fixes the issues... *more mumbles* MySQL status via CLI shows: mysql> status -------------- mysql Ver 14.14 Distrib 5.5.43, for debian-linux-gnu (x86_64) using readline 6.3 Connection id: 214 Current database: Current user: root@localhost SSL: Not in use Current pager: stdout Using outfile: '' Using delimiter: ; Server version: 5.5.43-0ubuntu0.14.04.1 (Ubuntu) Protocol version: 10 Connection: Localhost via UNIX socket Server characterset: latin1 Db characterset: latin1 Client characterset: utf8 Conn. characterset: utf8 UNIX socket: /var/run/mysqld/mysqld.sock Uptime: 19 min 30 sec Threads: 1 Questions: 4568 Slow queries: 0 Opens: 299 Flush tables: 1 Open tables: 292 Queries per second avg: 3.904 --------------

It seems to be, yeah. At least, for domains. I'll be checking on other packages here shortly.

You'll want @Licensecart to check in with ya. Ask him about the Full Service Blesta integration he does. It's about $250 iirc.

Hi, Is there a way to... oh, I don't know, simplify creating a product to sell for instance. That's very simple in WHMCS. in blesta you have to create a package group, a package, a product, also create the product in a provisioning module, and create a form for orders. In WHMCS you create a product, and you're done. Well, more or less done in WHMCS. But that's basically it. I have to admit, after I discussed this with a partner, I realized they were right when it comes to setting up packages and products. Can we move towards emulating WHMCS in this fashing? :c

Should be fixed... all the pages should now point to their own pages until we've finished configuring services and the like and link them into our billing system. Er... damn, I forgot about that one. I'll get to that ASAP.

New logo has been uploaded! Mostly the design is done now, I think... but man, those product boxes on the main index is driving me nuts... same for the separator bars that I can't seem to wrangle out properly. If anyone'd be willing to help, I'd be eternally grateful.

Yeah... I basically rm -rf'd the modules directory, unzipped the blesta zip that I still had when I initially set up Blesta (3.4.0-3.4.2 I think it was) and moved the appropriate directory back into place and chown'd to the owner of the account. Didn't change permissions or anything but... after moving that stuff into place, it worked A-OK perfectly. Permissions issue, I suspect. Either way, your solution did the trick.

1. Yep, it's meant to be there. It's quite okay! 2. Fixed. Turns out I needed to use the actual HTML code for — which resolved the issue. 3 & 4. I should probably ask LicenseCart and see if they'd be willing to look into this... 5. Yeah, I'm working on figuring out what's up here... I'll be asking LicenseCart to take a look at this. Actually, I just fixed this. Turns out the loader was causing the issue. Fixed that. Not sure how I managed to miss that... that's several times I've done it. I also fixed the issue of loading unsafe scripts which was the font.googleapis.com links on the HTML pages not being in HTTPS mode when loaded via HTTPS. Still waiting on the logo designer... I'm starting to get seriously annoyed by the fact that I need to chase the logo developer for updates. Edit: Struggling to get the home page looking right... I'm no good with design-related stuff and HTML. But servers and other things? I can get things fixed quickly. :|

... I derped hardcore on this one so this helped me double-check and make sure things were working well... So thanks for that, too, heh.

Reporting back: Removing the modules as you described and adding them back in resulted in no white pages again. Strange... I don't know what happened but I'm unable to reproduce it. Either way... Modules Installed and Modules Available is working, now.

That did the trick, it gave me access back. Alright, time to do this, one by one. We only had 5 modules activated at the time. InterWorx, Namecheap, cPanel, SolusVM and BuycPanel. We'll see which one did it. I'll report back as soon as I find out what the offending module was doing.

So correcting the paths and the like didn't seem to fix the issue. I'll note that Plugins > Available works just fine but not Modules > Available. I'm not entirely sure what else I can do to correct this issue, so far. I do see that instead of the usual 200 code... it's a 500 code, which means something is triggering an internal server error. Welp. Time to look at where it's at to find the ISE...

Erm... that might be it. >_> I was editing the structure.pdt to sync the header and footer... but I don't know if that might have had anything to do with it. Web server logs... AH, here it is: Odd. It seems to be... redirecting? Or something similar.