Our first release candidat is in the internal testing. Some new impressions ... Relese of our portal will be next week. Before you get the xenMiG Portal for a free 14 day testing.
View attachment 103831 View attachment 103832 View attachment 103833 View attachment 103834 View attachment 103835
A new version with all features for version 1.0.0 is ready. It will be here today or tomorror.The release will be this week-end? Tx
This isn't good for the design. Last 5/10/15 threads is a fix definition, but some days you got many new threads and sometimes zero. This isn't good for designFor exemple, top thread ranked by view count last 7 days etc.
Well, the TOP 10 threads this week, will be always 10 threads (except for small forum, but this is not a mandatory to use this option).A new version with all features for version 1.0.0 is ready. It will be here today or tomorror.
This isn't good for the design. Last 5/10/15 threads is a fix definition, but some days you got many new threads and sometimes zero. This isn't good for design![]()
The Release Candidate 1 of the xenMiG Portal
I copy the code before </head> and it´s ok so.I'll try the PageContainer, though.
<head>
<xen:hook name="page_container_head">
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1" />
<xen:if is="{$isResponsive}">
<meta name="viewport" content="width=device-width, initial-scale=1" />
</xen:if>
<xen:if is="{$requestPaths.fullBasePath}">
<base href="{$requestPaths.fullBasePath}" />
<script><xen:comment>/* Chrome bug and for Google cache */</xen:comment>
var _b = document.getElementsByTagName('base')[0], _bH = "{xen:jsescape $requestPaths.fullBasePath}";
if (_b && _b.href != _bH) _b.href = _bH;
</script>
</xen:if>
<title><xen:if is="{$title}">{xen:raw $title} | {$xenOptions.boardTitle}<xen:else />{$xenOptions.boardTitle}</xen:if></title>
<noscript><style>.JsOnly, .jsOnly { display: none !important; }</style></noscript>
<link rel="stylesheet" href="css.php?css=xenforo,form,public&style={xen:urlencode $_styleId}&dir={$visitorLanguage.text_direction}&d={$visitorStyle.last_modified_date}" />
<!--XenForo_Require:CSS-->
{xen:helper ignoredCss, {$visitor.ignoredUsers}}
<xen:include template="google_analytics" />
<xen:include template="page_container_js_head" />
<link rel="apple-touch-icon" href="{xen:helper fullurl, @ogLogoPath, 1}" />
<link rel="alternate" type="application/rss+xml" title="{xen:phrase rss_feed_for_x, 'title={$xenOptions.boardTitle}'}" href="{xen:link forums/-/index.rss}" />
<xen:if is="{$pageDescription.content} AND !{$pageDescription.skipmeta} AND !{$head.description}"><meta name="description" content="{xen:string wordTrim, {xen:helper stripHtml, {xen:raw $pageDescription.content}}, 200}" /></xen:if>
<xen:if is="{$head}"><xen:foreach loop="$head" value="$headElement">{xen:raw $headElement}</xen:foreach></xen:if>
</xen:hook>
<!-- Start WOWSlider.com HEAD section -->
<link rel="stylesheet" type="text/css" href="engine1/style.css" />
<script type="text/javascript" src="engine1/jquery.js"></script>
<!-- End WOWSlider.com HEAD section -->
</head>
At the moment we did some rework for our widgets and build some new. We got some questions why we offer only a few widgets and I try to explain.
Our widgets are very easy to customize. This demo is based only on our top thread widget. So you only need one widget for all of this and more ...
The portal
View attachment 106613
View attachment 106614
Only one kind of widget is needed for all this
View attachment 106615
And you will be able to customize this in the style editor (the common parts, the rest is included into a css file)
View attachment 106616
We use essential cookies to make this site work, and optional cookies to enhance your experience.