Forum Replies Created
-
AuthorPosts
-
Thanks for clarifying. Kriesi now has an idea for the next three elements ;-)
add_filter(‘avia_social_share_link_arguments’, ‘avia_add_social_share_link_arguments’, 10, 1);
function avia_add_social_share_link_arguments($args) {
$args[‘xing’] = array(“encode”=>true, “encode_urls”=>false, “pattern” => “https://www.xing.com/social_plugins/share/new?h=1&url=%5Bpermalink%5D&t=%5Btitle%5D”);
return $args;
}I dont think this is a good idea. I guess many users would like to have the option to display social share icons in a custom order. So why dont you introduce such an enhancemnet?
Thank you for your answer. But I talk about the social share buttons on blog posts and not about the social profiles in the header/footer.
Wie groß Deine Bilder sind ist Deine Aufgabe, nicht die des Themes. Enfold fügt nur das ein was Du über den Media Manager hochgeladen hast. Bearbeite Deine Bilder bevor Du sie auf den Server spielst, z.B. mit TinyPNG.
Well, then something is wrong in YOAST as I use it myself. The title (the one showing up on the browser tab) on paged blogs did not contain the page number until I changed the header.php. Anyway I have my solution. Keep on the good work.
Cheers
Michael
Well it is your decision. But your customer will be happy if this becomes a core feature or even an option they can modify from the settings page. If you neither change the core file nor add the filter by default every user of Enfold with paged blog pages will get “double tilte tags” errors displayed in Googles webmaster tools. Those users addicted to SEO won’t be very happy about it.
And for the community: the upcoming update for Enfold solves this issue.
Many thanks to Kriesi for the most wonderful theme and the ongoing support that seems to never sleep!
This reply has been marked as private.This reply has been marked as private.Finally with some customization: https://www.mensmaximus.de
I like Enfold and recommend it every day.
I had the same issue and found a workaround. Maybe it solves your issue too. Please see https://kriesi.at/support/topic/blog-pagination-6/#post-249965.
Please see my latest post at https://kriesi.at/support/topic/blog-pagination-6/#post-249965 for a workaround I found.
Please see my latest post at https://kriesi.at/support/topic/blog-pagination-6/#post-249965 for a workaround I found.
Update
To temporarily work around the issue until it gets fixed by Kriesi you can follow this instructions. Go to your WordPress admin panel and chose the following settings (dont forget to save settings in each step):
Settings -> Reading -> Front page displays => Your latest posts
Enfold -> Theme Options -> Frontpage Settings => select the page of your choice
Enfold -> Theme Options -> And where do you want to display the Blog? => select the ‘select page’ entry
(so in fact you select NO page for the blog at all)
Enfold -> General Settings -> Blog Style -> ‘use the advanced layout editor to build your own blod’
Create a page (e.g. blog), add the Blog Posts Content Element and modify the layout as you like (with pagination)
In Appearance -> Menu add the newly created page to the menu used as ‘Enfold Main Menu’.
Got to your website and click on the newly created menu item.
Your blog posts should load as expected and you should see the pagination.
A click on one of the pagination links should now load the corresponding subset of posts as expected.I have tested it with my development and production site with different layouts and everything seems to work well.
Regards
Michael
- This reply was modified 10 years, 8 months ago by mensmaximus.
Update
If you set the same page as front and blog page pagination is working. I guess the function avia_custom_blog() might be the key to the issue.
Sorry for highjacking your post but as I have the same issue and already found the bug I thought it might be useful to tell you:
https://kriesi.at/support/topic/blog-pagination-6/#post-249910
Regards
Michael
Sorry for highjacking your post but as I have the same issue and already found the bug I thought it might be useful to tell you:
https://kriesi.at/support/topic/blog-pagination-6/#post-249910
Regards
Michael
Update
If you set permalinks to standard and use the advanced layout editor to build the blog page a call to the blog page will have a url like
http://domain.com/?page_id=22
If you click on the second page in the pagination the resulting url will be
http://domain.com/?page_id=22&paged=2
This must lead to a 404 error because ‘paged’ must be ‘page’ in this case (is_page).
If you manually call
http://domain.com/?page_id=22&page=2
you will get the expected blog page containing the second subset of posts.This is definitely a bug within Enfold as it has been tested on a vanilla wordpress install with nothing else than enfold installed (no plugins at all).
Please fix this bug asap and test it with pretty permalinks as well (/%postname%/).
Thank you.
Update
As already mentioned in thread https://kriesi.at/support/topic/blog-style-advanced-layout-editor/ again this is an issues with the uri arguments.
The avia_pagination function tries to get the page/paged argument and fails.
if(get_query_var('paged')) { $paged = get_query_var('paged'); } elseif(get_query_var('page')) { $paged = get_query_var('page'); } else { $paged = 1; }
Therefor the fallback to 1 is triggered.
May this be an issue due to the usage of Nginx instead of Apache?
Update
Depending on the layout I choose in the blog posts content element within the advanced layout editor the link of the pagination changes. E.g. if I choose [single author, big image, excerpt, read more] the link under the page 2 end correctly with /blog/page/2/. But if I choose the grid layout page 2 points to the last displayed post on page 1.
Regards
Michael
This reply has been marked as private.This reply has been marked as private.This reply has been marked as private.Hi,
it seems to have been an issue with my child theme. I had relocated my base.css to the child and did some customization there. To solve the problem i have copied the base.css from version 2.6 to my child and implemented my changes again. Now images are shown as expected again. Sorry for any inconvenience I have caused with this “bug report”.
Regards
Michael
PS: The new header options rock! And i could remove all my custom css I had formerly to deal with the header except
#top .main_menu .menu>li:last-child>a { padding-right: 13px !important; }
to deal with the last menu item if you do not display the search icon.2nd PS:
The iconbox background color issue within a color section with alternate color scheme still exist:
https://kriesi.at/support/topic/colorsection-and-iconbox/I have noticed this effect since 2.5. However since my Chrome updates automatically I cant say whether this flaw would show up with an older release of Enfold and Chrome 32.
And of course this is a browser issue. And as I wrote many times it does not happen with each Chrome installation. Moreover I have provided detailed information which css parameters (duration and y2 coordinate of cubic-bezier) of -webkit-animation help to solve the issue. Together with the Chrome installation I have setup for you on a virtual machine you should be able to locate the issue which is definitely caused by the jQuery function fn.avia_sc_animation_delayed.
Because Safari shows a flaw to this seems to be a general webkit problem. For me this sounds like a reintroduced clipping issue (which has been reported many times for chromium). You can close this ticket as I workaround the issue by overwriting the css declaration. Since I found the workaround my posts where meant to provide you with as much information as possible to either fix the issue with the jQuery function or to file a report with Chrome. However now you and the community know the issue exist and how to fix it.
Regards
Michael
One more information. On the affected computers Safari displays a smooth animation of the icon as long as y2 of cubic-bezier is 1 ore less. As soon as y2 is above 1 the animation is a 2 step display (from 10% opacity and small icon to 100% opacity and full size icon from one second to the other).
-webkit-animation: avia_appear 0.7s 1 cubic-bezier(0.175, 0.885, 0.320, 1);
works in Safari and Chrome as expected-webkit-animation: avia_appear 0.7s 1 cubic-bezier(0.175, 0.885, 0.320, 1.275);
causes issues on the affected computersAgain, this happens only in conjunction with jQuery using setTimeout to add a class (.avia_start_delayed_animation).
It is definitely caused by fn.avia_sc_animation_delayed. Chrome on Android ignores the delayed start completely and therefore the animation works well. The css code to animate the icon is working well if not combined with jQuery (the delay). Still I have no idea why this happens only on Chrome and only on some computers.
As for now the only save way is to set the y2 coordinate to 1 (no bubble effect).
Did you use the WIndows VM? There you can see the issue live.
This reply has been marked as private. -
AuthorPosts