[WEswift]

What does “to hand” mean?

I have to be able to update an existing page AND keep the original style. The previously described workaround (of changing the aforementioned row setting to Full-Width Contained) didn’t work. So despite the “legacy” settings being stripped, I attempted to fix them and it didn’t work. How can we make this happen?

[WEswift]

Team – my row width issues are still unresolved after update: http://bit.ly/2dZhJof If I don’t edit the page only the first row of the page has a style issue (it’s text content extends to the page edges – missing left and right padding as desired). If I do update the page to attempt to fix that first row (changing all row Wrap Type settings to Full-Width Contained) then all the rows no longer extend to the window left and right edges. The rows only extend to the content width. Additionally, background parallax imagery disappears. Please see the attached screenshots for examples. Thoughts? Thanks in advance.

Attachments:

You must be logged in to view attached files.

[WEswift]

Multilayer parallax doesn’t seem to be working for me. Here’s my test page: http://bit.ly/2e8gOk3

I’ve used the above supplied code and even pulled in the example outerspace / asteroid / rock images. Thoughts? Thanks in advance!

[WEswift]

This reply has been marked as private.

[WEswift]

In my testing the setting is retained, but look of the row drastically changes after updating the plugin. Post update, Full-width Stretched pushes row content to the edges of the window (see attachment swift-f-current.png). Before the update this content had padding between it and the left and right edges of the window (see attachment swift-f-old.png). If I attempt to change Full-Width Stretched to Full-Width Contained, the containing rows do not extend to the left and right edges of the window (see attachment swift-f-fullwidthcontained.png). In addition, making this one change on the first row appears to perform the same change to all subsequent rows. Full-Width Contained is not visually different than Standard Width. Thoughts? Thanks in advance.

Attachments:

You must be logged in to view attached files.

[WEswift]

Ed – Why can’t that setting be retained / transitioned when updating the theme? That could potentially be a lot of work. Thoughts? -Paul

[WEswift]

Soooo strangely it’s working now. I went to edit the test page you made and I couldn’t get the Swift Page Builder to work. Then I made a brand new page and it worked there. Then it started working on existing pages. Strange – but at least we’re good now. Thanks for the assist!

[WEswift]

Hi Rui,

Thanks for looking into this. It looks like the update fixed it. Thank you!

[WEswift]

This reply has been marked as private.

[WEswift]

This reply has been marked as private.

[WEswift]

This reply has been marked as private.

[WEswift]

thank you that worked!

[WEswift]

Good workaround. I ended up employing the following:

@media (max-width: 1199px)
{
	.full-center #logo.has-img a > img
	{
		max-width: 200px;
	}
}

[WEswift]

Rui – Thanks so much for the clarification. I understand what is going on and this will really help me going forward. Thanks again. -Paul

[WEswift]

Rui – Firstly, thanks for fixing the issue. However, this seems like very odd theme prioritization. For testing purposes, I duplicated the News/Events page and made another widget area with sidebar one in it. When there is nothing set in Reading Settings > Posts Page, I get two columns of sidebars – as expected since we now have a right sidebar set in Theme Options > Archive/Category Options.

When I set the test page to be the Reading Settings > Posts Page it REMOVES the Widget Sidebar content area. That doesn’t seem like appropriate behavior. When I think about more local/specific settings (like in css) trumping more global settings, I would expect both sidebars to still appear in this instance. Why then would a theme setting REMOVE a content area? I don’t think a global Theme Options > Archive setting should be able to remove what I’ve specifically set as my page content. I can see now what is happening, but I would really appreciate some clarification on why this happens. My theory is that when a page is assigned to Reading Settings > Posts Page, the page uses a default posts page template. Is that close? Thanks again for the assist.

-Paul