John

i have create a feature request , this a good option not only to re-order widget but also to re-order native widget like transaction , services , invoices ....
http://www.blesta.com/forums/index.php?/topic/4594-option-to-reorder-widgets-for-client-side/

Oh, so it's not a plugin issue, but an issue with Blesta not allowing the re-ordering. Thanks for the insight!

I would like to see their client ID probably or client name if possible mate at the moment it shows the client ID as their database ID.
 
Also if possible have the notes display at the top of the other boxes It's a bit hard out of view for a notice?
 
As for the above here's our contribution for your module, feel free to add if you would like.
 
 
OLD design:

 
NEW design:
 

 
CODE to replace in: plugins/client_notices/views/default/admin_main.pdt
<?php echo $this->Html->ifSet($message); $links = array(); $this->Widget->clear(); $this->Widget->setLinks($links); $this->Widget->create($this->_("AdminMain.index.boxtitle_notices", true), array('id'=>"admin_main"), $this->Html->ifSet($render_section, null)); if ($this->Html->ifSet($notices, false) && ($num_notices = count($notices)) > 0) { ?> <div class="content_section"> <div class="inner" style="padding: 20px 20px 0px 20px;font-size: 14px;"> <ul> <li><?php $this->_("AdminMain.add.search_for");?>: <input id="system-search" name="q" type="text" /></li> </ul> </div> </div> <div style="padding: 10px 20px 0px 20px;"> <table class="table table-list-search"> <thead> <tr class="heading_row"> <td><span><a href="<?php echo $this->Html->safe($this->base_uri . "plugin/client_notices/admin_main/index/?sort=id&order=" . ($sort == "id" ? $negate_order : $order));?>" class="ajax<?php echo $this->Html->safe($sort == "id" ? " " . $order : "");?>"><?php $this->_("AdminMain.index.heading_id");?></a></span></td> <td><span><a href="<?php echo $this->Html->safe($this->base_uri . "plugin/client_notices/admin_main/index/?sort=client_id&order=" . ($sort == "client_id" ? $negate_order : $order));?>" class="ajax<?php echo $this->Html->safe($sort == "client_id" ? " " . $order : "");?>"><?php $this->_("AdminMain.index.heading_client_id");?></a></span></td> <td><span><a href="<?php echo $this->Html->safe($this->base_uri . "plugin/client_notices/admin_main/index/?sort=notice_name&order=" . ($sort == "notice_name" ? $negate_order : $order));?>" class="ajax<?php echo $this->Html->safe($sort == "notice_name" ? " " . $order : "");?>"><?php $this->_("AdminMain.index.heading_name");?></a></span></td> <td><span><a href="<?php echo $this->Html->safe($this->base_uri . "plugin/client_notices/admin_main/index/?sort=date_added&order=" . ($sort == "date_added" ? $negate_order : $order));?>" class="ajax<?php echo $this->Html->safe($sort == "date_added" ? " " . $order : "");?>"><?php $this->_("AdminMain.index.heading_date_added");?></a></span></td> <td><?php $this->_("AdminMain.index.heading_options");?></td> </tr> </thead> <tbody> <?php $i=0; foreach ($notices as $notice) { ?> <tr class="<?php echo $this->Html->concat(" ", ($i++%2 == 1) ? "odd_row" : "");?>"> <td><?php $this->Html->_($notice->id);?></td> <td><a href="<?php echo $this->Html->safe($this->base_uri . "clients/view/" . $this->Html->ifSet($notice->client_id));?>"><?php $this->Html->_($notice->client_id);?></a></td> <td><?php $this->Html->_($notice->notice_name);?></td> <td><?php echo $this->Date->cast($notice->date_added);?></td> <td><a href="<?php echo $this->Html->safe($this->base_uri . "plugin/client_notices/admin_main/edit/" . $this->Html->ifSet($notice->id));?>"><?php $this->_("AdminMain.index.option_edit");?></a>, <?php $this->Form->create($this->base_uri . "plugin/client_notices/admin_main/delete/" . $this->Html->ifSet($notice->id)); $this->Form->fieldHidden("id", $this->Html->ifSet($notice->id)); ?> <a href="<?php echo $this->Html->safe($this->base_uri . "plugin/client_notices/admin_main/delete/" . $this->Html->ifSet($notice->id));?>" class="manage" rel="<?php $this->_("AdminMain.modal.delete_notice");?>"><?php $this->_("AdminMain.index.option_delete");?></a> <?php $this->Form->end(); ?> </td> </tr> <?php } ?> </tbody> </table> </div> <?php }else{ ?> <div class="content_section"> <div class="inner" style="padding: 20px 20px 0px 20px;margin-bottom:-12px;font-size: 12px;"> <ul> <li><?php $this->_("AdminMain.index.no_results");?></li> </ul> </div> </div> <?php } $this->Widget->end(); ?> <script type="text/javascript"> $(document).ready(function() { $('#admin_main a.manage[rel]').blestaModalConfirm({base_url: '<?php echo $this->Html->safe($this->base_uri);?>', close: '<?php $this->_("AppController.modal.text_close");?>', submit: true}); }); </script> <script type="text/javascript"> $(document).ready(function() { var activeSystemClass = $('.list-group-item.active'); //something is entered in search form $('#system-search').keyup( function() { var that = this; // affect all table rows on in systems table var tableBody = $('.table-list-search tbody'); var tableRowsClass = $('.table-list-search tbody tr'); $('.search-sf').remove(); tableRowsClass.each( function(i, val) { //Lower text for case insensitive var rowText = $(val).text().toLowerCase(); var inputText = $(that).val().toLowerCase(); if( rowText.indexOf( inputText ) == -1 ) { //hide rows tableRowsClass.eq(i).hide(); } else { $('.search-sf').remove(); tableRowsClass.eq(i).show(); } }); //all tr elements are hidden if(tableRowsClass.children(':visible').length == 0) { tableBody.append('<tr class="search-sf"><td class="text-muted" colspan="6">No entries found.</td></tr>'); } }); }); </script> Table design thanks to Eric who did a module for me
 
 
New Client Side:

 
CODE to replace in: plugins/client_notices/views/default/client_widget.pdt
<?php if ($this->Html->Ifset($notice) ) { // Don't show this container when only rendering the widget section if (!$this->Html->ifSet($render_section) && !$this->Html->ifSet($is_ajax) && $this->Html->Ifset($notice) ) { ?> <div class="col-md-12"> <?php } echo "<div class='alert alert-danger' role='alert'><b>"; echo $this->Html->Ifset($notice->notice_name); echo "</b><br />"; echo $this->Html->Ifset($notice->notice_body); echo "</div>"; // Don't show this container when only rendering the widget section if (!$this->Html->ifSet($render_section) && !$this->Html->ifSet($is_ajax)) { ?> </div> <?php } } ?>

You can create an order page set to register.

Yes, we will be adding the ability for authenticated clients to see and order restricted packages they have access to. This will round up this feature nicely.

Set the package to restricted, and then on the client page under Account Actions, click Set Packages.

Set the package to restricted, and then on the client page under Account Actions, click Set Packages.

Bummer - would be good if autodebiting could be set from my end for all subscriptions.

As far as the Support Manager is concerned, a ticket is created independently from any note or reply text you add to it, so it would require additional logic to determine which reply was indeed created when the ticket itself was created (i.e. which reply is indeed the first)--if any reply was created at all.
 
I can see how it might be useful to show "New Ticket" as the subject rather than "Update to Ticket", but I think that is a relatively minor issue not warranting a separate email template by itself.
 
What you could do is update the Ticket Updated email template subject line to cover both cases of New and Updated tickets. If you edit that email template you can change the subject line to:
{% if ticket.reply_date_added == ticket.date_added %}New{% else %}Update to{% endif %} Ticket {ticket_hash_code} New tickets will then say "New Ticket" in the email subject, and updated tickets will continue to say "Update to Ticket".
 
To be more technical, this will evaluate that the ticket reply (the text you wrote in the ticket) was created at the same time that the ticket itself was created. In that case, it will show "New Ticket" as the subject. However, because the ticket and its reply are created independently of each other, it is possible that they may be created at a different second, causing some new tickets to continue to use the subject "Update to Ticket" instead. That is likely a rare occurrence.

Thank you guys (Paul/Tyson/Cody) for all your hard work (love the new smile eheh)

I'm talking about the people who already store credit cards. Also, it would just be an option for those who want it.

How would that work? If you had a value of 1 and a client mistyped their CC number when submitting a payment, they're going to be frustrated that they can't fix it and pay. Then they might fail to pay an invoice on time, say it's not their fault because the system didn't let them pay... and chaos may ensue afterward. Seems like it could be a hassle for legitimate customers.

Don't forget the Domain Manager!

Hello Blestars
 
Im back again (so many work in this last 3 months that I didnt have time to update and talk to you guys )
 
Cool 3.4 Now!
 
Its to bad that is still not included the new "Domain Managment"  
 
I have build a temporary solution, but dont have time to update all registrar modules to implement, also has to mess with one ore 2 core files, and I hate that
 
So, ++++++1 for Domain Managment on next release
 
I Think its a major priority the Domain Managment, higher than any outher extra like Mass Mail, Affiliate etc..
 
How can we sell Domains correctly, and manage them in full with "Mass Mail Plugin" or "Affiliate Plugin" ?
 
Just my 2 cents:P
 
Keepup the good work Paul/Tyson/Cody

Nice! Looking forward to testing it. +1 for the Domain Manager btw.

This was a restriction in Blesta for versions 1.x-2.x. It's no longer an issue in v3, their is no reason to reserve a range of ID's for staff any longer. Previously, staff and clients logged in at the same place and could use their ID or their email so it was necessary to prevent overlap to distinguish staff and client accounts. No longer.

Don't forget the Domain Manager!

Don't forget the Domain Manager!

Please add to "Access Control List -> Clients" permission for "Override price package"

My hero. I'm not sitting here saying everyone from users to basic staff should have the ability to do this. I'm saying that administrators, privileged super users that have the ability to control and edit every facet of the system, ought to be able to remove charges (or any other record) that doesn't belong. Now my test charges are an ugly stain on my system, and are horrible for audit purposes

Sounds like a good idea for a plugin
 
*If* you could delete transactions, you probably wouldn't want all your staff to be able to do the same. Making money disappear in one area, sometimes mean it is re-appearing in someone's pocket, off the books. That's money laundering. If you can tell your auditor that Blesta doesn't allow you to delete transactions, then it makes you look a whole lot better and raises fewer questions. I'd rather explain why there's a voided test transaction than be under the heat lamp. In the grand scheme of things, it doesn't take up much space in your database, and space is cheap.

I'll +1 that password shouldn't be included by default however you can add it in if you wish. As for the email rotate I'm going to -1 that since a customer will probably go well you didn't email me that before... Yes we did!

Unless there are some major issues discovered (unlikely), final release will be next week.

I'd pay $4 for 512GB of RAM.

like {client.firstname} {client.lastname} {client.fullname} +1