admIBI

Thanks for the solution. Shoulda known that with WP the fix was going to be a plugin. I installed a different plugin because that one had a few bad reviews. Also, since this functionality is native to the Parallax theme, it seems like it would be possible to tap into that functionality by adding a bit of code to an anchor. Regardless, thanks for resolving this.

Thanks for your response.

That video describes what I already have: a link that has a snap-to transition to the anchor point. What I want it to have the smooth-scroll transition (that’s built into the AccessPress Parallax theme) that the menu has.

I’m pretty sure the solution is to simply add a CSS class to the link to activate the jQuery funtion.

Click the buttons on the sliders at https://ibrandintegration.com and you’ll see that the transition is immediate instead of a smooth scrolling transition.

Thanks again for helping me out.

How about going to ‘Theme Options >> General Settings >> Select Header Layout’ and selecting the second header layout that has your logo centered at the top with the menu centered below your logo.

Version 1.19 fixes this bug.

Thanks for adding that functionality, AccessPress. And thanks for fixing the menu bug in 1.18.

Cool. Thanks.

You’ve got to be kidding me. Using blog posts to create content on non-blog web pages is a fundamental design flaw. Or it’s done purposely to force users to pay “customization” fees. Both the Parallax theme and the Lite theme have some web elements that are added via a page (ie: not posts), so they’re not included in the blog stream. Why would you code it so some elements are added by creating a new page while others are added by creating a new post? ALL non-blog content should be created via widgets or pages. Only blog post content should be added using posts or blog categories, regardless of whether the theme is free or purchased.

I’m going to mark this as resolved, but to really solve this, AccessPress developers need to divorce themselves from the idea of using posts to update web elements like sliders and website sections like a list of services. Using posts to input these website (ie: NOT blog) elements means they turn up in ‘Recent Posts’ section in the sidebar, which just ain’t right.

You can see the problem in the last section with the red background. I created that section using a page titled ‘Services’, and that page only includes the two paragraphs with heading for the two services. It DOESN’T include the blog posts, but somehow they’re being included in that page. And the list of services isn’t being formatted by the ‘Service Section’ layout coding, only the posts are.

Thanks for replying, MMX. When I tried that the path became: mysite.com/blog/blog/posttitle

Anyone?

How do I prevent the posts used to change the slider images (or any post used to change/update website elements like the welcome post section, testimonials, events, etc.) from being displayed in the ‘Recent Posts’ section? I only want those ‘posts’ to change/update the website, not be part of the blog archive. Thanks.