As usual, Jaxel doesn't respond to feature suggestions.. Unless it of course is something he needs at his own site.
I dont expect to add many more widgets into the CORE product... This is a FRAMEWORK; if you want a new widget, ANYONE can make it. This addon already has over 30 included widgets, no other widget framework has even half of that.Why Jaxel don't respond to feature suggestions. What a shame.
Do you have the widget framework enabled?I am not sure what I am doing wrong. But the default Article page isn't showing any widgets on the right sidebar. The widgets show in the middle or left hand side. But no right sidebar. Help!
Highly doubt there is a super simple solution for this. Basically you need to define the "og:image" meta tag for that page. IMO since this addon is heavily focusing on articles now, custom (and hidden) facebook thumbnails wouldn't be a bad feature to include.I'm assuming that whatever image attachment you select as the icon of an article is the preview image that will be displayed when the article is linked in Facebook? Is there a way to select the icon for an article (for facebook purposes) but not have it appear as an icon on the front page?
<xen:include template="EWRporta2_Global_Above" />
{template}
<xen:include template="EWRporta2_Global_Below" />
<xen:include template="EWRporta2_Global_Side" />
<xen:include template="EWRporta2_Global_Above" />
{$userTemplate}
<xen:include template="EWRporta2_Global_Below" />
<xen:include template="EWRporta2_Global_Side" />
This will be implemented in the next version... You can see it working here:I'm assuming that whatever image attachment you select as the icon of an article is the preview image that will be displayed when the article is linked in Facebook? Is there a way to select the icon for an article (for facebook purposes) but not have it appear as an icon on the front page?
#1 - This is precisely because the xfrock's widget framework is GLOBAL while XP2's widget framework is not. I spent a lot of time thinking about that decision when I made the widget framework. Making it global is actually really easy, and a lot less work than the way I've done it. Making it global is as simple as saying "always extend into the XP2 ViewPublic"; but I decided instead to make it "only extend into the XP2 ViewPublic if the current ViewPublic is in a specific list". The advantage of this is the widget framework won't add unnecessary resources to check for layouts on pages which it shouldn't need to check for layouts because you dont plan on ever using a layout there... the disadvantage of course, you've already pointed out.Feedback:
I was trying to add a custom layout to a personnal page (using it's own view and template). With the widgets framework developped by xfrocks, that's really easy. With yours you need:
- To extend the view in the global options - I think this parameter should be available in the layout config page like you did for the template name ; when you save the layout you could use a cache system to merge it with the setting from the global options
- To give the template name... but this template must have been formated with the below codes:
To be honest, I haven't found time to look at it, but you should be able to use a template wrapper to avoid this. Get the user template in the view, use it as a param when you call your template wrapper which code would look likeCode:<xen:include template="EWRporta2_Global_Above" /> {template} <xen:include template="EWRporta2_Global_Below" /> <xen:include template="EWRporta2_Global_Side" />
That would avoid to edit the user templateCode:<xen:include template="EWRporta2_Global_Above" /> {$userTemplate} <xen:include template="EWRporta2_Global_Below" /> <xen:include template="EWRporta2_Global_Side" />
What are your layout settings? What existing layouts do you have? What are their priorities?Yes it is
View attachment 99568
I am completely confused on what you are suggesting here...Quick suggestion that might be useful to people who want to add a mega menu to their navigation.
Basically, it would be a syntax code such as this one <xenporta2:cat1+cat2_5/> adding that to a template would simply display the last 5 news with cat 1 AND 2 attached (and cat1-cat2 would display articles from both categories)
The use of widget is nice but I think that being able to seek articles everywhere should be the best addition to XenPorta 2.
And I don't know if it's already the case (I can't try it the way I want for now) but we definitly need an option to just seek articles from cat 1 AND cat 2. not cat 1 + cat 2.
If the option is checked, it changes the way the widget works, if it's not, nothing change.
Did you test it on the default skin?Single default layout. I am not sure how to check the priority on the default layout.
View attachment 99579
send me a PM with your forum and some admin credentials and I will look at it for you... Also, put it in debug mode.Yes, default skin.
This doesn't show any widgets on the right side. Recent Threads works
View attachment 99581
This works great.
View attachment 99582
Should I uninstall and install it again?
Okay, looking at your forums... it looks like you have the BD Widget Framework installed. The BD Widget Framework takes over the sidebar on every page in XenForo (this is not a bug, this is by design, its doing exactly what its supposed to do). When you have BD Widget Framework, it means the sidebar is being controlled by BD, not XP2.Yes, default skin.
This doesn't show any widgets on the right side. Recent Threads works
View attachment 99581
This works great.
View attachment 99582
Should I uninstall and install it again?
Thanks! Got the widgets back after disabling BD widgets. Can you add this to the FAQs to save other people some timeOkay, looking at your forums... it looks like you have the BD Widget Framework installed. The BD Widget Framework takes over the sidebar on every page in XenForo (this is not a bug, this is by design, its doing exactly what its supposed to do). When you have BD Widget Framework, it means the sidebar is being controlled by BD, not XP2.
This is why the sidebar isn't showing for you... because BD widget framework controls it, not XP2.
This will be implemented in the next version... You can see it working here:
http://8wayrun.com/threads/lost-swords-costume-pack-from-yamatogawa.18571/
I am completely confused on what you are suggesting here...
<div class="navigation">
<ul>
<li>HOME</li>
<li>FORUMS</li>
<li>LASTEST NEWS
<ul>
<li><xenporta2:cat1_1/></li>
</ul>
</li>
<li>MEMBERS</li>
</ul>
</div>
Thanks for your all explanations. I didn't know that.#1 - This is precisely because the xfrock's widget framework is GLOBAL while XP2's widget framework is not. I spent a lot of time thinking about that decision when I made the widget framework. Making it global is actually really easy, and a lot less work than the way I've done it. Making it global is as simple as saying "always extend into the XP2 ViewPublic"; but I decided instead to make it "only extend into the XP2 ViewPublic if the current ViewPublic is in a specific list". The advantage of this is the widget framework won't add unnecessary resources to check for layouts on pages which it shouldn't need to check for layouts because you dont plan on ever using a layout there... the disadvantage of course, you've already pointed out.
#2 - I actually thought about this one too... But again, I chose against it because of the disadvantages. Not every page can be wrapped with the layout grid the same way; specifically if the page has an existing sidebar. Sometimes, you may wish to add a layout grid to a page, but keep the existing sidebar; putting it into a homogeneous wrapper would preclude this option.
You don't actually need to edit templates... you can do it with a simple Regular Expression template modification:For the second point, when it's one personal addon, I don't care to add the extra includes in my template. When it's someone else, I don't like to customize templates to avoid to review them after an update. So may be a small option in the page layout with an optional auto wrapper would be nice. I get your point, but most of the time this simple wrapper will work as expected.
#(^.*$)#s
<xen:include template="EWRporta2_Global_Above" />
${1}
<xen:include template="EWRporta2_Global_Below" />
<xen:include template="EWRporta2_Global_Side" />
#(^.*?)(<xen:sidebar>.*?</xen:sidebar>)(.*$)#s
<xen:include template="EWRporta2_Global_Above" />
${1}
<xen:include template="EWRporta2_Global_Below" />
<xen:if is="{$widgets.sidebar}">
<xen:include template="EWRporta2_Global_Side" />
<xen:elseif is="!{$layout.layout_sidebar}" />${2}</xen:if>
${3}
We use essential cookies to make this site work, and optional cookies to enhance your experience.