serge

i recommand Licensecart , as is a active user here and can help also from outside the forum .

Thanks! CORE-1582

The 6 hours lock from Blesta can be found here,

Line 1909 in : /app/controllers/cron.php :
-----------
if (strtotime($last_run->start_date) < strtotime(date("c") . "-6 hours"))
---------

so it's does make sense to lock still runing cron task, but what will be the chance they end if there are not done in a couple of mins, I think, even in case of hundred of thousand of operations that should never be very long ?

6 hours is maybe excessive in my opinions, I will be more confortable with something like very max 1 hours or even 40 mins seem still to me very very fine.

Describe the issue you're experiencing.
------------------------------------------------
when price period is "onetime" & when ordering package & being in client area at the "complete" step,
 
Paypal button for subscription is displayed.
 
if customer select it, it's will give error at PayPal website: incorrect payment method
 
So, Paypal subscription button should NOT be displayed at Blesta for onetime price period
 
 
 
Provide detailed steps necessary to reproduce the issue.
----------------------------------------------------------------------
 
1/
having prices with period:
 
onetime
 
and also
 
monthly, day, year
 
 
2/
Having this option enabled in Blesta & PayPal Payments Standard:
 
One time and subscription payments when possible
 
3/
 
order a package being onetime period
 
&
select subscription
 
 
observations:
---------------------
 
at order & complete step, Paypal subscription button should NOT be displayed at Blesta for onetime price period
 
 
other: maybe other gateways could be concerned by same bug, I did not checked

For exemple they bill you for what is activated in the moment of generating invoice .
The same as cpanel licences with cpanel .
Nice feature .

in proforma PDF , the proforma containe the "invoice number"  , and this is not possible . it should show proforma number as label .
 
proforma = proforma number (label).
invoice = invoice number (label).
 
this is very easy to fix .

Solved all issue now. I need to make a profound test before release .
Sequencial proforma is done
Invoice date is date of closed proforma , no probleme in dates
Invoice paid , saved auto in a folder with pdf format , so dont worry if the client change thier info , yiu have a saved pdf with old info .

new release
2.2.0
-add proforma invoice sequencial numbering option.
-add new events handler .

adding this in /config/blesta.php  did the job:
if ($_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') $_SERVER['HTTPS']='on';

adding this in /config/blesta.php  did the job:
if ($_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') $_SERVER['HTTPS']='on';

Great, I had "dejavusancondensed", and by swiching to "helvetica", it give me now 10KB for PDF invoice with logo

The font you are using...

i have a idea to add it , but not sure if it work .

don't forget , we are here always to help

In the dashboard when you have a lot of invoices, services,etc, dashboard page can be LONG., and not all customers will scroll down so much.
 
Each widget can display each up to 20 lines by widget's pages., so if you have in this order
 
Widget 1: Invoices (20 lines)
Widget 2: Services (20 lines
Widget 3: Transactions (20 lines)
Widget 3: Supports (20 lines)
 
That do mean, "Transaction" is starting at +40 lines, and not all customers will presume it's bellow & will scroll down so much.
 
So that why I created quick links for widgets at top & at bottom of dashboard, see pictures.
 
Here the methods:
-----------------------
 
in     /app/views/client/YOUR-THEME/client_main.pdt

just after:

<div class="col-md-9 right_content">

Add:

              <a name="top"></a>
             
                |  <a href="<?php echo $this->Html->safe($this->client_uri . "#services");?>">Services</a> |
              <a href="<?php echo $this->Html->safe($this->client_uri . "#transactions");?>">Transactions</a> |
              <a href="<?php echo $this->Html->safe($this->client_uri . "#tickets");?>">Tickets</a> |  
    <br>
    <br>



At the end of file

just after:

?>


Add:

   <center>
               | <a href="<?php echo $this->Html->safe($this->client_uri . "#top");?>">Back to Top</a> |
               <a href="<?php echo $this->Html->safe($this->client_uri . "#invoices");?>">Invoices</a> |
              <a href="<?php echo $this->Html->safe($this->client_uri . "#services");?>">Services</a> |
              <a href="<?php echo $this->Html->safe($this->client_uri . "#transactions");?>">Transactions</a> |
              <a href="<?php echo $this->Html->safe($this->client_uri . "#tickets");?>">Tickets</a> |  
   </center>


-------------

in     /app/views/client/YOUR-THEME/client_invoices.pdt

At very beginning:

Before:

<?php


Add:


<a name="invoices"></a>

----------------

in     /app/views/client/YOUR-THEME/client_services.pdt

At very beginning

Before:

<?php


Add:

<a name="services"></a>

--------------------------

in     /app/views/client/YOUR-THEME/client_transactions.pdt

At very beginning

Before:

<?php


Add:

<a name="transactions"></a>



-------------------------

in          plugins/support_manager_addons/views/default/client_widget.pdt

At very beginning

Before:

<?php


Add:

<a name="tickets"></a>
 

updated to 2.0.0
+ fix bug in plugins disable/uninstall popup modal .
+ added support to add edit delete CMS pages . no chaneg needed in the cms portal .
for CMS portal , add a new page , the URI is the path to that page in the url adress .
exemple , new page with uri "about-us" canbe accessed with the url

http://yourdomain.com/blestaurl/about-us enjoy the plugin .

my next version of admin tools plugin , i have added option for cms portal , you can create/edit/delete page from cms without topucing any files in cms plugin .
i have tested it and is working .

This is hardly the best way of doing it but it works. (Don't judge me )
 
In /app/views/client/bootstrap/javascript/jquery-client-3.2.0.js method blestaLoadWidget find:
var temp = $(data.content); after it put the following:
// Append the widget to the page if (data.content.indexOf("services") >= 0)     $(container).prepend(temp); else     $(container).append(temp); That's it!
 
edit: forgot to mention which method to change lol

If your bank decided to only put the posted dates and leave out the column with the transaction dates on your credit card bill each month would you be happy about that? Would you be able to match up your gas receipts to the posted date? Now picture doing that for a year of transactions. You may think it does not bother you so nobody else should need it but I'm sure the day your credit card statement had posted dates and no transaction dates you would immediately see the importance of what I'm saying. In my country most of our accounting systems were inherited from UK and customers prefer to have actual dates as opposed to the date posted. I hope this example helps to illustrate my concerns.

I agree on the resume. :-)
 
I would like to add:
Paid invoice sequential number must have an increment only by 1, if not there will be missing number in the time chronology, it's illegal

I agree on the resume. :-)
 
I would like to add:
Paid invoice sequential number must have an increment only by 1, if not there will be missing number in the time chronology, it's illegal

@Paul: Simplifying things
Pro-forma invoices should always have sequential not reused numbering.
Final invoice should always have the date of creation/converted (im not talking paid date), and should always have for tracking/search propose the pro-forma old number and also all client details saved (simple way as an array) to not be changed ever.
Resolving this will be all good

you could tell to your hosting company or consider changing?

I also experienced this reported bug before.

All of this is coming because 2 differents documents type (unpaid invoice and paid invoice) are sharing at some point same sequential numbering in a single column "id_value" at Table "invoices" in database.

1/ Proforma (unpaid invoice or quote by the way)

Are not really sequential number by now in Blesta because it's re-use old previous number that was existing before (before the switch at payment "date_closed"), so at different time, you can send to different customers , proforma using an old used sequence number "id_value" that was again released.
 
So, it's a traceability & commercial issue. All proforma should be related to an unique content/proposal.

 

2/Paid invoice

should have their very own sequential numbering, created from the payment date (this sequential number column is now missing in Blesta, this new column could be "id_paid")

What accountability request in EU (but not only there), is Paid invoice number are sequential and without numbering interruption (missing number between paid invoices), and the more easy is just to base the number sequence on the payment date, and not like now from proforma sequence, because not all proforma will be paid...
-----------

Unpaid  vs paid are 2 separate "documents" type for the sequencing number
UNPAID:
sequencing is based on creation of the document itself ("date_billed" in table "invoices"), it's ever "id_value", but it's should be persistent (never be changed when invoice is closed)

PAID:
sequencing number should be based on payment date more exactly "date_closed" in Table "invoices", so it will be more suitable to have a new column "id_paid" in Table "invoices"
  In place of:  like Blesta is working now by only sharing "id_value" for both type (unpaid & paid).


So my proposal to solve the issue, will be easy to implement as it's do not change a lot the way Blesta work and for old data, it's will be easy to create the missing paid invoice sequencial "id_paid" number with an Blesta upgrade & SQL query, as "date_closed" is ever know in the database.
 
I past here bellow more detail I given in this post:

http://www.blesta.com/forums/index.php?/topic/3306-pro-forma-invoices-numbering-are-not-sequential/page-3


 

The 6 hours lock from Blesta can be found here,

Line 1909 in : /app/controllers/cron.php :
-----------
if (strtotime($last_run->start_date) < strtotime(date("c") . "-6 hours"))
---------

so it's does make sense to lock still runing cron task, but what will be the chance they end if there are not done in a couple of mins, I think, even in case of hundred of thousand of operations that should never be very long ?

6 hours is maybe excessive in my opinions, I will be more confortable with something like very max 1 hours or even 40 mins seem still to me very very fine.