Search results

yeah its been really quiet this last few months, not a lot of support lately.

I don't follow, can you post exact steps to reproduce this issue please? The whole site is never cleared and re-written, that is not even possible.

these notices are not a big deal and should not be displayed on a production site. That said, this will be fixed up for next release. :) thanks for the heads up

span is inline element, so you may need to make it inline-block. Also you are mssing the url segment on your background-image declaration this should work: background-image: url('/skins/default/images/pokal1.png'); width: 100px; height: 174px; display: inline-block;

At the moment, you would need a custom plugin to build a category menu that would include the counts. I will move this to the feature request forum, I'm sure we had this available at one time many years ago.

Add this to skins/default/user.css .bg-dark { background: #000 !important; }

these 2 child templates have been removed for next release.

nicolecarmine.ch/blog/ site does not resolve yuamb.ch is just slow, that is the screenshot after waiting 4 seconds of load time, white with preloading gif in teh middle. blogspot is blocking our screenshot server, totally unable to resolve that domain. not sure whats going on with...

admin -> content -> manage languages search for that phrase and edit as needed.

nope sliders will work fine, as long as they are not massive and slowing the pageload down to a point that it doesn't finish loading in time. Can you provide a couple sample URL's that are rendering black?

Updated hotfix. Patches a small index issue in the installer/updater where users may encounter this error on install regarding index on payment logs Fatal error: Database error in "/home/xxxxxx/public_html/install/index.php" on line 1235 Specified key was too long; max key length is 1000 bytes in

I believe you mean the OG image You can add these to your child/wrapper.html template: <meta property="og:image" content="https://yourdomain.com/image.jpg"/> <meta property="og:title" content="Your Title"/> <meta property="og:description" content="Your description."/> <meta...

yes, templates in /child/ simply override the default skins. So any edits should be made in /child/

That is my best guess

I just tried a test submission and indeed, got an error message with no highlighted field. As Basti mentioned above, this is most likely a custom join field added in the admin panel but not added to the join form template.

strange, I will submit a few tests on your list today and see if I can duplicate.

Sent via PM.

you will need to edit child/wrapper.html find: <a class="nav-link" href="{$list_url}/join/"> Replace with: <a class="nav-link greenlink" href="{$list_url}/join/"> Then add this to skins/default/user.css .nav-link.greenlink { color: green !important; font-weight: bold; }

no problem, these are edited in table_row and table_top_row templates.

Hello, all of this is done in wrapper template. Its a basic bootstrap template so you can use bootstrap documentation to help with HTML layout.