joejb

Apologies. Found out what is making the empty sidebar appear.

Thank you. this is useful to me. I would like to ride on the original question to ask: On my blog page, space appears on the right for a sidebar. Is there some CSS I can use to override this so the posts will appear across the full page.?

Hello again. This time I write to acknowledge my mistake in writing about the second non-menu, non-header-button, in-page link. I said that this link positioned its target well when the menu-header is fixed to the top of the screen, and does not position it well when the menu header scrolls away. I was wrong on both accounts. My apologies.
Nothing needs to be modified for the case that the menu-header is not fixed to the top of the screen. The issue is only the positioning of destinations of general in-page links for the case when the menu-header is fixed to the top of the screen, thereby hiding some of the page.

In case you are curious how my thinking went astray, I feel I owe you an explanation. Here it is. My mistake was that I did not realize that since the destination of my second link was relatively far down the page, the link could not position it at the top of the screen — its positioning was limited by the impossibility of scrolling the bottom of the footer above the bottom of the screen (or window)! Now that I am aware of that, I realize that the second link is behaving just as one should expect. When the menu-header is not fixed to the top of the screen (it scrolls away), the positioning of the destination of my second in-page link is limited by how close that destination is to the footer (which is fixed to the bottom of the screen). As a result, that destination is about 1 inch shy of the top of the page. In my ignorance, I took this to be incorrect. When the header is fixed to the top of the page, that 1 inch is hidden by the menu-header, and it looks like the destination of that link has been perfectly positioned on the screen–pure coincidence, but I did not realize that.

Could Bento provide an option that the blog page would not display the date of a sticky post? This would provide an easy way to have a heading full width across the native WP blog page as described in my earlier post on this topic.
In addition, this option might be useful in other ways–there is probably a variety of reasons for people to choose not to display the date of a sticky post.
Thanks.
Joe B

mistake. excuse me

• This reply was modified 7 years, 1 month ago by joejb.

Hi Michael,
I am using Bento.
I am very much a novice, so I hesitate to take a stand here, but the issue appears not to be theme specific. On the Bento forum I read that Bento uses the blog page native to WP.
Any help/insight you can give would be appreciated.

The above method may work also, maybe even better, for the Shop and Single Product pages. However, I am not familiar with these pages, and so cannot say.
Joe B

I can offer a way to create a header across the full width of the native blog post page. It’s not perfect, but pretty good. Create a post which starts off with an image. Using PageBuilder set up a single column row, and insert the SiteOrigin image widget, and upload an image. Click on the “Edit Row” option in the menu that that appears when you hover over the spanner of that row in Pagebuilder. In the window that comes up, go to the “Row Styles” menu on the right, click on “Layout”, scroll down to “Row Layout” and in the box select “Full Width Stretched”. Click “Done” at the bottom right hand corner of the window. You will be returned to the main editing page of the post. In the “Publish” box at the top of the right hand column, edit the “visibility” to make the post sticky. You will now have a post that has an image full-width across the whole blog page. Of course you can add to the post, below this image, any text you like through inserting further rows using PageBuilder. Do not give the post a name. This image now appears at the top of the native blog page, full width across the page.

The flaw is that on the blog page, showing through the left hand side of the image is a date of posting, which is also a link to the original post which is the source of the header now appearing across the blog page. Maybe someone in the forum may know how to get rid of this date?
Thanks, Joe B

Looks like we aren’t quite “on the same page.” I’m talking about non-menu non-header-button same page links. In the web page just after the hero image, there is a sentence with two same-page links; the anchors are “Music of the Unicorn” and “me”.
With header fixed to top of screen, which is how it is set now, the second link positions it’s destination well, the first does not. Both destinations are set through css class of relevant row.
As I read our conversation, you have stated your intention to make all such links work well in the next version of Bento. I am just offering some detail as to how they perform now –and expressing the hope that you can make both links perform well both for header fixed to top of screen and for header set to scroll away.
Hope this makes things clearer.
Thanks again, Joe B

Hi. The website is gloriaconly.com .
With the heading fixed, the first link on this page does not locate the destination well on the screen. The second link does. I think this is as I reported before.
However, in regard to the case when the header is not fixed. There have been changes–not that I have made, maybe due to something you have done with the theme?
At some time today when I have set the header to scroll with the page, both links in the page located their destination perfectly on the screen. However, now this is not the case; Now wth the header scrolling the first link works well and the second doesn’t.
I really want to thank you for your time on this. I do appreciate it.
Sincerely, Joe

Thank you. I look forward to the addition of the extended functionality.
Thanks also for the PS.
I hope you will be able to give the extended functionality for both cases — fixed heading and not fixed heading. I mention this because I suppose that having the functionality for the single-page primary menu items might apply only to the case with the fixed heading.
Moreover, I have found the following (but do not understand it): When the heading is fixed (heading does not scroll away) the first of my two in-page links (which both use the row css class to mark destination) does not locate its destination well and the second does. When the heading is not fixed (heading does scroll away) the first link does locates its destination well and the second does not.
I hope that in the next version of Bento both links will work well in both situations.

In my previous post I had code which is not preserved. The relevant sentence is:
“Using the text editor in Siteorigin Editor Widget I added code around AAAA like this AAAA and then inserted aaaa in the class field for the attributes of the row that I wanted to be the destination of this link, and similarly for BBBB.”
This sentence should be:
Using the text editor in Siteorigin Editor Widget I added code around AAAA like this
(a href=”#aaaa”)AAAA(/a) and then inserted aaaa in the class field for the attributes of the row that I wanted to be the destination of this link, and similarly for BBBB.
Here I use () instead of arrow signs as my attempt to preserve everything as text.

Thanks.
It seems that my theme has been automatically updated to 1.8 — and without giving me any notice of that.
When I go to the Bento manual that comes up as version 1.7.1, This seems to be the latest since it contains the changes you made on basis of this conversation, though the changelog seems to have stopped in June.

Yes, I do still have trouble even though I am running Bento 1.8. But I am not directly concerned with The call-to-action button in the header or the single-page-mode. I mentioned them because I thought they manifested the same problem that I am having.

I have text on a web page that says something like “Something here about my book AAAA and something here about BBBB.” Using the text editor in Siteorigin Editor Widget I added code around AAAA like this AAAA and then inserted aaaa in the class field for the attributes of the row that I wanted to be the destination of this link, and similarly for BBBB. [I got that idea from the way version 1.7.1 of the manual explains how to set up the one-page-mode.] But even though I am using Bento 1.8, that method has the problem of showing a place too low down on the page — the right location is being hidden by the page header, just like happened for the button on the Bento theme before you corrected it.

Can you help me with this? My work-around has been to delete the identifier I inserted in the CSS class field for the target row, and to insert in some text that appears above that location. By trial and error I find the best place to insert this. This works but is an unsatisfactory way of doing things, and does not give neat results when the screen size changes. So I turn to you for advice.

Please understand that the above is my total knowledge of code. I picked it up through googling on things I was trying to do.

Thanks for your attention, and I apologise for not being clear enough on my specific problem previously.

I’m confused. How do I find out which Bento version I’m using?
What is coming live now — 1.8 or 1.7.6?

Do your changes only help with making the one page mode, or do they help in general with using links and buttons for bringing specific locations within a page precisely to the top of the visible area?
Thank you,
Joe Becker

As a complete novice, a lot was very clear on first working with Bento. However, I wanted more help in learning how to get masonry tiles working well. For example, I don’t think the manual mentions that the image on the tile is sourced from the feature image of the relevant post, and the text is sourced from the title of the post (except for the case of a quote post!). Perhaps I missed it and this is in the manual– in that case, I would be grateful if you would point me to it since I would learn better how to use the manual.

Fine modification to the description of the quote format for posts.
By the way, there is a typo in the description of the aside format for posts. the word “thoughts” lacks a “t.”

I also ran across a different problem, that is manifested in a main Bento demonstration webpage. I will bring that up in a new post to the forum.
Happy New Year.