Licensecart

[Bit Bayou]

If I rotate my phone, it does look better... and yeah, I'm using the built in Android browser.

 

[Michael]

If I rotate my phone, it does look better... and yeah, I'm using the built in Android browser.

Yeah my default one looks rubbish haha.

 

My new wallpaper:

 

[Paul]

Looks good!

 

Are those the same colors as the blesta logo?

[Michael]

Looks good!

Are those the same colors as the blesta logo?

Thank you and Paul they are I checked hex

[HIGGINS]

Hey,

Why don't you pick a template on Themeforest and cusstomize it?

 

http://themes.truethemes.net/Sterling-HTML/page-template-homepage-jquery.html

But there are a lot more and you can customize the colors, too.

[Michael]

Hey,

Why don't you pick a template on Themeforest and cusstomize it?

 

http://themes.truethemes.net/Sterling-HTML/page-template-homepage-jquery.html

But there are a lot more and you can customize the colors, too.

not sure I'd rather learn the gist of Bootstrap and do it myself and that way it's not a cheap layout anyone can buy.

[Michael]

Our website is complete: http://licensecart.com/site/

 

Hoping to release it on the same day as Blesta to the public. I will be working on a new one though with Bootstrap 3 RC1 now that I've fallen in love with that framework haha.

[stapler2025]

Your site takes an exceptionally long time to load for me.

[Michael]

Your site takes an exceptionally long time to load for me.

Ah yeah that's because you've visited for the first time, it's calling the prices from the API.

[SkylarM]

Ah yeah that's because you've visited for the first time, it's calling the prices from the API.

I'm trying to refresh and it's REAAAAALLY bad.

[Tyson]

Yeah, 20 seconds to load the site is too long. Try to cache some data, remove some of the javascript if possible, and use smaller thumbnails rather than resizing large images.

[stapler2025]

Ah yeah that's because you've visited for the first time, it's calling the prices from the API.

 

You shouldn't be calling prices from the API on every single pageload that displays prices.

 

And it doesn't work like that, it's not a "first time" thing - its every page load, because every single time you load a page that calls the prices, you're calling the API.  It doesn't cache those unless you set it up to do so.

 

I do understand that you're trying to be fancy and all, but how much time do you really save by having the pricing automatically updated on your website?

[Michael]

I believe it was a client abusing the service but thankfully just me and them are on my site server. But it is a require_once code and its the api from the devs. There's a thread about it in contribute forum.

[iAlex]

What do you mean it is a require_once?

 

That still requires it every page refresh, require_once just makes sure that it only includes the file once in a single page, not for every refresh.

 

http://php.net/manual/en/function.require-once.php

 

It looks nice, it just loads pretty slowly.

[Michael]

What do you mean it is a require_once?

 

That still requires it every page refresh, require_once just makes sure that it only includes the file once in a single page, not for every refresh.

 

http://php.net/manual/en/function.require-once.php

 

It looks nice, it just loads pretty slowly.

I don't understand what you mean by having it so it's only included on a single page? 

 

Code we got given by Devs: http://staging.blesta.com/forums/index.php?/topic/592-display-prices-on-your-website/

 

If you don't include it how will it connect to the api to get the prices by setting cookies? air?

[iAlex]

I don't understand what you mean by having it so it's only included on a single page? 

 

Code we got given by Devs: http://staging.blesta.com/forums/index.php?/topic/592-display-prices-on-your-website/

 

If you don't include it how will it connect to the api to get the prices by setting cookies? air?

 

You seem to think that by using 'require_once' it won't need to keep including it after a refresh when it does..

 

With the script in that post you linked, using just 'require' instead of 'require_once' would do exactly the same thing.

 

No need to act childish with sarcasm, when I'm just trying to state a point.

[Michael]

You seem to think that by using 'require_once' it won't need to keep including it after a refresh when it does..

 

With the script in that post you linked, using just 'require' instead of 'require_once' would do exactly the same thing.

 

No need to act childish with sarcasm, when I'm just trying to state a point.

None of them is as you call it cache it for the next person.

[Bit Bayou]

Well, while not necessarily the best option, you can definitely use cookies. Load the API on the first visit, then set a cookie with the DISPLAY prices. Caution: Don't use that price when calculating at checkout! But yeah, get the prices once, set a cookie for like 24 hours, then use the cookie data on all the other page loads.

 

Basically set up the code that gets the price from the API and creates the cookie in a function called something like getPriceFor($item) then you can do something like:

 

$price1 = ( empty( $_COOKIE['item1Price'] ) ) ? getPriceFor('item1') : $_COOKIE['item1Price'];

 

 

That way, it only hits the API once every so often to update the cookie. You could then use a quick code to force a cookie refresh when/if the prices change later... Just thinking out loud

 

---- 

 

Definitely make sure you fight things like cross site scripting too if you go this route...

[Paul]

I would cache it to disk. serialized array written to a file, read the data from the file instead.. then, randomly on page load make another API call and overwrite the file. 1% of page loads should be enough.

[iAlex]

I would cache it to disk. serialized array written to a file, read the data from the file instead.. then, randomly on page load make another API call and overwrite the file. 1% of page loads should be enough.

 

This would be the best option, caching it to a file in php is the easiest way, would only take a few minutes to implement, shouldn't use cookies when you don't need to.

[Michael]

I would cache it to disk. serialized array written to a file, read the data from the file instead.. then, randomly on page load make another API call and overwrite the file. 1% of page loads should be enough.

 

I've never heard of that before? is that like the call to home you have got for blesta?

[Paul]

I've never heard of that before? is that like the call to home you have got for blesta?

 

No, it has nothing to do with licensing. It's just a common way to do caching. There's no need to make slower API calls for every page load when the data isn't changed frequently. This is more similar to what w3tc does for Wordpress.

[iAlex]

I've used something like this before; http://codecanyon.net/item/php-simple-cache/4169137

 

It basically saves the page as a HTML page and you can set how long that cache lasts, after that it will read and save the page again over the last one.

 

Therefore it won't call the API every reload, it will just read what was on the page at the time of the cache, you can set the expire from anywhere between an hour, or a month.

[Bit Bayou]

shouldn't use cookies when you don't need to.

 

well sure, and I didn't suggest it..just implied that it is possible 

[Michael]

I've used something like this before; http://codecanyon.net/item/php-simple-cache/4169137

 

It basically saves the page as a HTML page and you can set how long that cache lasts, after that it will read and save the page again over the last one.

 

Therefore it won't call the API every reload, it will just read what was on the page at the time of the cache, you can set the expire from anywhere between an hour, or a month.

wicked thank you.