[resolved] Future Request
- axew3
- w3all User
- Posts: 2883
- Joined: Fri Jan 22, 2016 5:15 pm
- Location: Italy
- Contact:
Re: Future Request
on fly, so with no guarantees, maybe try this to see if will fix:
- axew3
- w3all User
- Posts: 2883
- Joined: Fri Jan 22, 2016 5:15 pm
- Location: Italy
- Contact:
Re: Future Request
ps check the <ul element how i have edit it
and all li elements.
p.s This has not been applied to avatars mode, where there are table and td elements and not ul li , and need to be fixed about little things more, like links, but let see the first result.
and all li elements.
p.s This has not been applied to avatars mode, where there are table and td elements and not ul li , and need to be fixed about little things more, like links, but let see the first result.
-
- User www
- Posts: 63
- Joined: Sun Feb 26, 2017 8:33 am
Re: Future Request
I see what you have changed. I have uploaded it now but it looks it didn't have any effect.
-
- User www
- Posts: 63
- Joined: Sun Feb 26, 2017 8:33 am
Re: Future Request
Regarding your 1.6.6 topic you said
CODE: SELECT ALL
<ul class="" style="list-style:none;margin:auto auto auto 0px">
to class (or id) that your theme use for ul li elements on widget.
I have to add this to my last topics and login widget to have the same lettertype as my wordpress theme?
<ul class="???" style="list-style:none;margin:auto auto auto 0px">
??? = <ul id=\"recentcomments\">";
CODE: SELECT ALL
<ul class="" style="list-style:none;margin:auto auto auto 0px">
to class (or id) that your theme use for ul li elements on widget.
I have to add this to my last topics and login widget to have the same lettertype as my wordpress theme?
<ul class="???" style="list-style:none;margin:auto auto auto 0px">
??? = <ul id=\"recentcomments\">";
- axew3
- w3all User
- Posts: 2883
- Joined: Fri Jan 22, 2016 5:15 pm
- Location: Italy
- Contact:
Re: Future Request
didn't read this sorry ... yes exactly, you can apply both id or class to an element, the difference is that an id can be applied only to one single element, while classes can be applied to any instance of any element on page. I imagine you should have resolve, or not?
But on next version 1.6.7 if possible, 1.6.8 at max, the above will be possible to be done into config page, so at update you do not need more to apply any time these changes directly into phpbb_last_topics.php file.
The <table> and all elements inside will be moved inside <li> widget elements to be exactly as WP code on widgets is.
And all should result so working perfect on any theme that use default WP structure. If needed, you'll apply same class to ul or li element, but on wp_w3all config, where will be available fields settings about, to avoid the above explained about re-apply css changes into last topics file at any plugin update.
But on next version 1.6.7 if possible, 1.6.8 at max, the above will be possible to be done into config page, so at update you do not need more to apply any time these changes directly into phpbb_last_topics.php file.
The <table> and all elements inside will be moved inside <li> widget elements to be exactly as WP code on widgets is.
And all should result so working perfect on any theme that use default WP structure. If needed, you'll apply same class to ul or li element, but on wp_w3all config, where will be available fields settings about, to avoid the above explained about re-apply css changes into last topics file at any plugin update.
- axew3
- w3all User
- Posts: 2883
- Joined: Fri Jan 22, 2016 5:15 pm
- Location: Italy
- Contact:
Re: Future Request
p.s to add avatar into login widget, it is necessary to add just this:
after line
on file views/login_form_include_iframe_mode_links.php
OR
views/login_form_include_noiframe_mode_links.php
by the way on next version the entire code about this will be replaced by the new corrected one.
Code: Select all
echo '<li>' . get_avatar(get_current_user_id()) . '</li>';
Code: Select all
echo '<ul class="" style="list-style:none;margin:auto auto auto 0px">';
OR
views/login_form_include_noiframe_mode_links.php
by the way on next version the entire code about this will be replaced by the new corrected one.