The Oracle PHPlib has been modified to work with defined CLOB columns to permit text larger than the approximately 4000 character varchar() limit. For now the new 3.1 'langterms' column is the only CLOB, as terms and conditions may well go over 4000 characters. CLOBs can handle about 2 gigabytes of text.
We are very, very close to a 3.1 release. This will be the best FishCart ever, without question.
Today is a good day to say the least. In the past few hours we have successfully run HTML confirmation email straight through Smarty to completion. There were several key pieces that had to be hunted over the past few weeks, all culminating into the last few hours, then...success. Smarty wants things done in one way, and one way only thank you very much.
What we end up with, is the ability for the end user to write a standard HTML template for their confirmation emails. The structure for Smarty is logical, if you want the Billing First Name in a certain place in the template you would type: {$billing.firstname} last name: {$billing.lastname} . End users don't have to care about anything past that, and in my opinion that is worth alot.
Product display in the confirmations will be returned in a pre-formatted block from the php script. Basically proddispfixed.php rebuilt for Smarty. It will need to be included via the include_php function in Smarty. The code for the end user templates looks like this:
{include_php file="ph2.php" assign="proddisp"}
{$proddisp}
I tend to ramble when excited, but honestly I believe this will benefit FishCart greatly. Until next time, God Bless.
After almost starting from scratch again I feel much happier with it now. It will not only be able to work with MySQL but with PostgreSQL too.
The first release (hopefully within about 1 week from now) will only be able to work with MySQL, PostgreSQL will follow soon.
Today we successfully pulled a template stored in a mysql database, ran it through Smarty and printed it to the screen in a browser. This method is more useful because it doesn't require the template to ever become a physical file. This was accomplished in two distinctly different ways. First we created a resource document in Smartys plugins directory then called it from our php script. Second we created the needed functions and registered the resource inline in our php script. The second way shows more promise of flexibility and ease of use because we can easily construct the query on the fly. This is a foundational piece of getting Smarty to yak with FishCart. There are definately more miles to trudge, however this is exciting.
A new webflag will be added. This changes new lines from the product short description and description to br.
Data inside the database is not modified, it's just the output.
This flag will be available in v3.1
Just checked in the first complete rework of the country tables. This splits the original table into two tables. One contains the language dependent, installation independent elements of the country, the 'countrylang' table; the fields in this table never change regardless of FishCart configuration. The other contains an entry for each FishCart defined language; this serves as a join table to bind to the language dependent portion for the country name and ISO codes.
This part of the rework has been much more detailed than originally thought, but the structure is solid and normalized. The present design is very much a collaborative effort of the developers, especially B. and Dan Smith.
If this checks out as quickly as I hope, we should be close to a formal 3.1 release. Release has been delayed longer than anyone wanted, but we will have a much more stable, useable release for it.