Jump to content

kpmedia

Members
  • Posts

    139
  • Joined

  • Last visited

Posts posted by kpmedia

  1. You can use the routes.php but I've not got experience messing with getting routes to work my way:

     

    See: http://www.blesta.com/forums/index.php?/topic/1733-short-order-routes/

     

    Perhaps give an example of what you mean, with the URL from my first post.

     

     

    Yes you can use .htaccess to rewrite urls but don't forget to add conditions rules first, otherwise if you just add rewrite rules you will get internal server error every time

     

    Perhaps give an example of what you mean, with the URL from my first post.

  2. The default language is overwritten by updates. That's no good.

    Is it as simple as creating a new language?

    English is what I'd want, so renaming it to something random would work?

     

    I'm either not seeing docs on this, or I somehow missed it.

  3. Ah! That should be the default setting! That works.

     

    Now question #2 --

    How to insert the "summary" (ticket title) into the email?

    That is also a must, for quick scanning of emails.

    And that, too, should be the default setting.

     

    Aside:

    I'd really like to get a list of variables, as you find with vBulletin and WordPress. If I know those, I'm generally pretty good about reverse engineering or write new code. Both have a decent primer (crash course) on coding for that app, and I was able to follow along with it okay (and have for many years now). I see a lot of potential in Blesta, and it'd be great if I could make what I want (and share it) like I do with vB and WP.

    Note: I see the developer manual, but I'm not seeing what I need in there.

  4. I'm going to edit the client frontend to appear more like WHMCS.

     

    And then the admin backend to be more like WordPress.

     

    I can manually change the templates. I may try to share them here, when I'm done.

     

    I like Blesta, I really do. It has an easier-yet-customizable ability unlike WHMCS or ClientExec. But some areas are still very beta feeling compared to those, or even other CMS like WordPress. It reminds me of Xenforo. It's good, but it's not mature yet. Sadly, it may need several more years, though I wish it was quicker. WHMCS already went though that, and is only now mature.

  5. OnApp is cheapo grade cloud platform.

    Other panels are not much better with it, from what I've seen in recent years.

     

    Usually when a vendor needs a real cloud (VMware, etc), they need a powerful support app. Blesta is good, but it's not primetime. That's just not who's using it, hence the lack of demand.

  6. Well, what about entirely removing the menu, and manually create a new one with CSS?

    I'd just assume go that route, as I'm not fond of the current menu anyway,

     

    For that matter, I'd just assume do the same to the admin backend. That thing drives me nuts. I want dropdowns!

     

    EDIT -- Yep, got it. That's what I'll do. Manual CSS menu, here I come! And while I'm at it, I'll try to tweak the overall design.

  7. In the next build , wen the Blesta 3.2 go stable, we will add the option to revert to original if you whant.

    The option to revert to original woll be simple, it will only remove the "Spam" and "Detleted" status, will move all "Spam" and "Deleted" tickets to "Closed status", and will remove the extra field "Name" from Tickets where are stored the "From Name Emails", and finaly will delete all files, and replace by original files.

     

    ^ How do you do this?

  8. The main reason I want to use this is for the bubbles and merging abilities.

     

    But I have a hard time trusting 3rd-party scripts from individuals. When the author loses interest, then we're screwed, as updates that break it are always going to happen. I've been there dozens of times over the years.

     

    I wish this mod simply added features to the existing support system, and not replaced it altogether. Better yet, I wish that the Blesta would just integrate these things into the core.

     

    The biggest item is the ability to import/export between the two support systems.

  9. See attached.

     

    post-239-0-71369200-1427706042_thumb.jpg

     

    - I don't want to give clients the ability to add more contacts.

    - I don't want "Payment Accounts" to show up, as it's confusing. It's a useless menu item when you're taking Paypal and mailed payments.

    - The "account not set up" warning goes to the unwanted payment page.

    - The only way to receive invoices is via email. So again, a completely useless warning needs to be removed.

     

    I've been told several of things are "in the templates" -- but where? I don't see it.

     

    Blesta is great, but it has a lot of confusing things. Don't give clients too much credit. They're often not that smart.

  10. I've read that Blesta is now using Bootstrap.

    Where can I read more on it?

    I tried to search for it with Google, but there's more than one "bootstrap" from what I can tell.

     

    (The main reason I'd like to research it is for some better design. I'm not fond of the menu system used by Blesta, and want dropdowns.)

×
×
  • Create New...