Daniel B

If anyone would prefer a full page like this:
 

 
You can replace /plugins/announcements/views/default/client_main_view.pdt
 
with:
<?php // Don't show this container when only rendering the widget section if (!$this->Html->ifSet($render_section)) { ?> <div class="col-md-12"> <?php } echo $this->Html->ifSet($message); $this->WidgetClient->clear(); $this->WidgetClient->setStyleSheet($this->view_dir . "css/styles.css", array('id' => "announcements_styles")); $this->WidgetClient->create($this->_("ClientMain.view.boxtitle_announcement", true, $this->Html->ifSet($announcement->title)), array('id'=>"announcements_client_main_article"), $this->Html->ifSet($render_section, null)); $this->WidgetClient->startBody(); ?> <div class="announcement"> <!--- <aside> <div class="col-md-3 "> <div class="panel panel-default" id="accordion"> <ul class="list-group"> <li> <a href="<?php echo $this->Html->safe($this->base_uri . "plugin/announcements/client_main/");?>" > <?php $this->_("ClientMain.view.root_directory");?> <span class="pull-right"> <span class="glyphicon glyphicon-home"></span> </span> </a> </li> <li> <a href="#" > <?php $this->_("ClientMain.view.date");?><?php $this->Html->_($announcement->date_added);?> <span class="pull-right"> <span class="glyphicon glyphicon-time"></span> </span> </a> </li> </ul> </div> </div> </aside> --> <div class="col-md-12 "> <ol class="breadcrumb"> <li> <a href="<?php echo $this->Html->safe($this->base_uri . "plugin/announcements/client_main/index/");?>"> <?php $this->_("ClientMain.view.root_directory");?> </a> </li> <li class="active" > <?php $this->Html->_($announcement->title);?> </li> </ol> <div class="well well-sm"> <h2><?php $this->Html->_($announcement->title);?></h2> </div> <?php if (!empty($announcement)) { ?> <div class="well well-sm"> <div class="article_view"> <?php echo $this->TextParser->encode("markdown", $announcement->body);?> </div> </div> <?php } else { ?> <div class="col-md-12"> <h3><?php $this->_("ClientMain.view.announcements");?></h3> <div class="alert alert-info"> <p><?php $this->_("ClientMain.view.no_announcement");?></p> </div> </div> <?php } ?> </div> </div> <?php $this->WidgetClient->endBody(); $this->WidgetClient->end(); // Don't show this container when only rendering the widget section if (!$this->Html->ifSet($render_section)) { ?> </div> <?php } ?>

Square please lol since I had CubicWebs  

It is a little bit different, but I think the original one if completed would allow your request to work . It's a paradox, they are the same but different.  Do you wanna be the square or the rectangle?

Wow...you made this fast!  So fast I didn't even get a chance to respond to your initial feature ideas thread (though, I did delay a bit in my reply).
 
Having annoucements pop up as alerts under the navbar on the portal or in the client area (setting per annoucement?) would be pretty awesome as well, with an option to close them if you'd like (so once someone sees it once they can close it and not see it again).

Fixed and updated in GITHUB
 
any other bug found report it here .

I can do some minor edits, but I am sure i will probably break something if i try to do anything more than that. LOL
I have a great respect for those that can code.
I'll try.
Thanks
(i'll sign up soon at MyHostingBoard)

Take screenshots of all the UI areas you think need to be improved and open feature requests threads about it...the devs are very responsive to these things .
 
In the mean time, every single page of the UI can be modified.  Blesta is almost completely open source.

the same as this request ?
 
http://www.blesta.com/forums/index.php?/topic/1306-department-level-ticket-auto-replies/

I was thinking  maybe a idea to have a auto reply option on the departments for vacations / out of hours / away from the office etc. Bit like the "no reply for 24 hours" but maybe a check box to enable / disable.

Hello All .
we bring exclusive content , this time is the Announcement plugin .
A very clean and simple Announcement plugin for Blesta , allows you to post announcements , and make them , Publicly for all or based on clients groups and service's packages.
the plugin can  :
    add/edit/delete Announcement.
    List All Announcements
    Restriced Announcement based on client Group And packages .
    Show widget announcement in client side .
    Option to enable/disable widget in client side.
    Setting to show announcement in full or mixed views.
    Set how much announcement should be displayed in widget client
TODO LIST :
- show widget announcement in client side . Done
- option to enable/disable widget in client side Done
- set how much announcement should be displayed in widget client Done
- allow share buttons or announcement
- allow client to ignore announcement message .
- hide announcement in widget after X days .
- Add RSS announcements (just the public announcements)
- add setting to show announcement in full or mixed views Done
Some screenshoot :
Admin Side :

 
Client Side :
 

 
client widget :
 

 
This Plugin is tested in our test server , no bugs at the moment , in this weekend we will add support for client widget .
as always the installtion steps is :
1 - download the file http://blesta-addons.com/plugin/store/main/item/22/
2 - upload the announcements folder inside plugin directory .
3 - goto plugins , and install Announcements  Plugin .
4 - enjoy the free content .
If anyone wants to have it on their portal you can use this code: (thanks to @Licensecart)
    {% if plugins.announcements %}<div class="col-md-4 col-sm-6 portal-box">         <a href="{client_url}plugin/announcements/client_main/">             <div class="well">                 <i class="fa fa-info fa-4x"></i>                 <h4>Announcements</h4>                 <p>You can see all the latest news here.</p>             </div>         </a>     </div>{% endif %} It will only show up if the module is installed.
This plugin require Basic (Bronze) subscription

What I did a while ago (and thanks for reminding me to redo this on my new install) is just to remove the option of selecting a username.  That way it forces people to use their email as their username...and would then catch this issue if it happens again.
 
Remember though, you'll have to redo this edit for any update that replaces this file since it's editing a core file.
 
Edit this file: /plugins/order/views/templates/standard/types/registration/signup.pdt
 
Find and [either remove or comment out]:
<div class="radio"> <label> <?php $this->Form->fieldRadio("username_type", "username", ($this->Html->ifSet($vars->username_type) == "username"), array("id"=>"username_type_username")); $this->_("Signup.index.field_username_type_username"); ?> </label> </div>

I knew I should have saved it...but, +Bacon should always give at least some sort of advantage, that's like a natural law or something...so maybe I'll try again later

well blast.
 
+Bacon

well Naja, now we know how to get anything implemented! lol
 
@Paul can we just shorten it to +3 in the future?  Or maybe +2 +1?

I knew I should have saved it...but, +Bacon should always give at least some sort of advantage, that's like a natural law or something...so maybe I'll try again later

+Bacon is correct, too bad it was applied to the same feature request. 

The secret phrase to guarantee task creation for a feature request is much like TOTP. It changes frequently and cannot be used again. Failure to guess correctly causes the feature request to be ignored for a random amount of time between 5 seconds and 37,000 years.

Well, since naja7host had 3 plus one's in there.. CORE-1387

I've posted this a few times in different threads, so I figured it might be beneficial to have it's own thread for those who might go looking for it in the future.
 
Currently, it is not possible to merge accounts in Blesta which can sometimes cause an issue with the same client registering twice (once using their email and again using a custom username).
 
A quick fix for this (which will likely need to be redone after Blesta updates) is to remove the option to register with a custom username.
==============================
 
Edit this file: /plugins/order/views/templates/standard/types/registration/signup.pdt
 
Find and [either remove or comment out]:
<div class="radio"> <label> <?php $this->Form->fieldRadio("username_type", "username", ($this->Html->ifSet($vars->username_type) == "username"), array("id"=>"username_type_username")); $this->_("Signup.index.field_username_type_username"); ?> </label> </div> The result will look like this on the registration form:

Almost since the day I started using Blesta, I have been manually editing a core file to remove the option for clients to register with a username (http://www.blesta.com/forums/index.php?/topic/3178-remove-option-to-register-with-custom-username/)
 
Adding a setting to the admin side of things to allow us to select if we want to allow usernames would be much appreciated.  Personally, I prefer to have client information be uniform, so having some clients with custom username and other with emails as usernames just bugs me (and for a billing system, I just prefer emails anyway).

Yup, he's already checked that and said it was set correctly (this is what I initially thought of as well).

It's not available yet, but I'm in the process of spec'ing it out, and we'll be starting development soon. The goal is to have it included in 3.4, and possibly release it as a beta prior to 3.4 beta but it will depend on how quickly it comes together, and if we run into any issues.

For ticket auto-replies, do you mean the initial ticket received email? You can currently set an auto-close ticket response per department, but not the initial auto reply.
 
One thing we're planning is CORE-1358 which allows for custom email templates to be created. It may be possible then, after that, or in conjunction with that, to allow the selection of different templates in different areas of Blesta.. including auto-replies and separate templates per department.
 
So, this suggestion may fit well with that task, and be dependent on it.

best unit of time ever lol

Yeah, sorry about that. I didn't realize the variable wasn't available to the template.
 
3.3 is in a feature freeze, and as of just now we have a 3.3.0-b1 build that's in QA.