Despite all mistakes they do, it's understandable that they delete thirty bees in the forum. As we all know, thirty bees is just a better ps. It means it's a big treath to the them... It wouldn't the first fork, which "overtakes" the main project.
At the moment it's hard for me to imagine, how I could use this. Is it basically for local testing purposes?
I use multistore... How does it work there?
Which sitemap module?
I think user should define, what should be in. Of course there should be option for categories, products, blog, manufactures, suppliers and cms pages.
Hello
I know, that we have some server experts here. Maybe somebody could explain, how caching is working. It confuses me, that there are many different caching methods. As far as I know, I have the following:
nginx cache
redis cache
smarty cache
full page cache
Additional there is the browser cache, right? Which one is doing what? Where are the risks?
I am always afraid that visitor could see outdated informations. Let's say I change price of a product. Is there a risk, that customer sees the old price? What if I change tpl files?
Tipp: You can find this out very easily by your own. Just use a modern browser where you can select an element to inspect it. It shows immediately that its h1. To find out which tpl file, you just read body id="". The id normally tells you the tpl file!
This is the blog module from kpodemksi. I have some issues to make it work.
It seems to be caused by the rewrite system. Unfortunately this module now even breaks other frontControllers.
For example I get: Fatal error: Call to a member function isAccessGranted() on null in /home/genzo/publichtml/modules/phsimpleblog/controllers/front/single.php on line 33
But when commenting this function out, I get a 404 error.
@mdekker could you solve this?
@Havouza said in How create a link like this?:
This is the code in the tpl.
To me it looks if a target is hardcoded here, all links will open in a new tab. Solution for that is to only place links here that should open outside the shop
<ul id="footercustom_link_informations">
<li class="footercustom_link_title footercustom_title">{$blocktitle1|escape:'html':'UTF-8'}</li>
{foreach from=$blocks1 item=block name=loop}
<li>{if $block.link}<a href="{$block.link|escape:'html':'UTF-8'}" title="{$block.title|escape:'html':'UTF-8'}">{/if}{if $block.title}{$block.title|escape:'html':'UTF-8'}{/if}{if $block.link}</a>{/if}</li>
{/foreach}
</ul>
Yeah you could solve it in your tpl file. The solution which comes to my mind is a bit ugly. But you could use something like:
{if $block.id==anynumber}target="_blank"{/if}
I don't use this module, so I don't know if you have access to the id...
You have html error in it. You mess up with quote sign (").
Yours:
<a href="https://webadmin-lin.demo.plesk.com:8443/smb target ="_blank"" title="Plesk Control Panel">Plesk Control Panel</a>
Correct:
<a href="https://webadmin-lin.demo.plesk.com:8443/smb" target ="_blank" title="Plesk Control Panel">Plesk Control Panel</a>
@Traumflug said in Onepage Check-out like presta 1.7:
I wonder all the time why people ask for a one-page checkout all the time. There is one, right in thirty bees, standard installation. Just enable it in Backoffice -> Preferences -> Orders -> General. Works just nicely.
Is this the same as in PS? Cause this is no real onepage checkout. User have to save address first. But to be honest, I wonder too why so many are screaming for one page checkout.
Our experience shows that people get confused, when they have to fill in too much on a single site. I only like one pages checkout for registered customers with saved addresses.