wakabayashi

I doubt he will fix it, since he doesn't even upgrade his module anymore...

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?

There is a menu "topic tools". I can do it there. But not sure, if it is because I am moderator. Anyway: somebody did it :D

You are welcome! Feel free to mark it as "solved".

``` {$blocktitle1|escape:'html':'UTF-8'} {foreach from=$blocks1 item=block name=loop} {if $block.link}{/if}{if $block.title}{$block.title|escape:'html':'UTF-8'}{/if}{if $block.link}{/if} {/foreach} ``` Try it like 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 =&quot;_blank&quot;" 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.

I am not yet on tb on live server and removed the font from my theme ;)

Oh yeah Michael is right :D @mdekker why is it done like this? It confuses me a lot ^^

Not sure if this is problem. The phone icon on the top is loaded...

I see... Not sure what is the problem, since I add FontAwesome by CDN. Try to add this to global.css .fa-check:before { content: "\f00c"; }

But where is the page, which doesn't work?

Hm I don't understand your problem. Is your site live? Or can you show us your html code?

You can use cms.css file, which is in your theme folder. If you wanna have specific rule for one page, you can use selector "#cms-id". Ofc you should replace id with the number.

Did my method not work, or you just decided to make a new installation?

Have you changed shop url in backoffice (SEO & URLS)? If you use multistore these settings are stored under mutlistore. Not sure if you have to change anything else. In config folder there is a file "settings.inc.php". In it you find a constant 'PSDIRECTORY_'. Maybe this has to be changed as well...

Hello I just installed the blog module and it looks solid :grinning: :thumbsup: Still I want to share improvements ideas: Preview a post for author. This is very helpful when you are creating a post, but don't want it to publish yet. Author widget. Instead of just showing blank name, it would be nice to have an avatar & little description. Translation option. You offer a field "available for these languages". That's a very nice feature, but I would disable it, if user has only one languaged installed. I would also consider, to preselect default language. Link blog with ecommerce. I think in the longer run, the blog should be linked deeper with the ecommerce system. It' should be easy, to insert links to a product. Also reversed: to insert blog posts on categories or products pages. Shortcodes. This is related with the previous point. It would be amazing to have a shortcode system, which devs/designer could use. Imagine of something like this: [smalllist idcategory=12 products=5] Edit: * RSS Feed * Including links to sitemap How do you like about my ideas? Feel free to add your own in this thread!

I think you could solve it with css media queries. Otherwise fluid typography could be helpful: https://www.smashingmagazine.com/2016/05/fluid-typography/

@MockoB I am not from germany, but in switzerland situation with "Rechnung" is very similair. Well if he forgets, you remind him. We do this first by email and later own with a letter. When we finally switched to TB we will add Paypal and CreditCard. At the moment we only have Rechnung and two swiss methods.

No it's not the same. If you aren't from germany you should stay away from "Rechnung".

As @MockoB said, it's "Rechnung". This payment method is super ugly for us merchants. You send your goods without any payment. You add an invoice to it. When the customer is happy with the products and dont ship them back, he can pay it with bank transfer. The risk is all at merchant. If the customer doesn't pay the invoice it's very hard to do something. We lose quite a lot money that way. Other payment methods are: SofortÜberweisung Paypal CreditCard

In don't get your question. Are you asking which payment methods are popular in germany?

@dynambee I think this discussion helps @mdekker to make a good checkout. It's not so easy to customize checkout for coders/designers... It has to be good in core already...

Yeah that's the thing. It's just pschology effect. I believe best thing is this: - New customers order without entering a password - After the order was sent, they are asked if they wanna use a personal password. - In backoffice I would handle them all the same, based on their email. If somebody reoders with same email - Case 1: He didn't chose a password. -> He won't see any personal data in front office -> psychologial effect. - Case 2: He did chose a password -> he logs in & checks out fast as hell ;) Edit: @mdekker, @lesley. I just wondered if it would be possible to have just a single email field. With ajax we check, if there already exists an account/password. If yes we display immediatly a password field and customer can login. If the email is new or was only used as guest, he will again follow the whole checkout path. I think this would be a userfriendly way to combine account & guest checkout. But not sure if ajax call will be fast enough, to have a smoth user expierence.