Thanks! Please check the following:
Copyright (c) 2021 Axyn Technology (Ricardo Ruggiero)
All rights reserved.

This software is provided as is without any guarantees or warranty. In association with the product, Axyn Technology makes no warranties of any kind, either express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, of title, or of non-infringement of third party rights. Use of the product by a user is at the user’s risk. ALL SALES ARE FINAL.

NO REPRESENTATIONS OR WARRANTIES, EITHER EXPRESS OR IMPLIED, OF MERCHANTABILITY, FITNESS FOR A SPECIFIC PURPOSE, THE PRODUCTS TO WHICH THE INFORMATION MENTIONS MAY BE USED WITHOUT INFRINGING THE INTELLECTUAL PROPERTY RIGHTS OF OTHERS, OR OF ANY OTHER NATURE ARE MADE WITH RESPECT TO INFORMATION OR THE PRODUCT TO WHICH INFORMATION MENTIONS. IN NO CASE SHALL THE INFORMATION BE CONSIDERED A PART OF OUR TERMS AND CONDITIONS OF SALE.”

WordPress Embed

For Stacks 4.x
WordPress Embed Stack
A new way to bring WordPress content into a Rapidweaver Website.

WORDPRESS EMBED

WordPress Embed takes a new approach to add WordPress content to your Rapidweaver Website.

One of the issues of embedding dynamic content (such as blog, pages, post categories) is that we don't know how many items will be displayed, and therefore the height of the content.

That's where the WordPress Embed comes in!

Just drop the WordPress onto your Stacks page, set the location of your WordPress installation, then enter the slug for the WordPress page, blog category, or single post, and the WordPress Stack does the rest.

WORDPRESS REQUIREMENTS:

The WordPress installation must be placed the same site where the Rapidweaver files are published. Although not required, it's recommended that the WordPress installation be placed in a folder at the root of the website. For example, it could be placed in a folder called 'wp'. In that case if the domain was 'example.com' the wordpress "site" would be: https://example.com/wp

However, the WordPress installation can be placed any folder which is part of the Rapidweaver site. For example, if your website is placed in a sub-folder (not at the root), the Wordpress installation folder can also be a sub-folder of the site. For example, is the base URL of your site is: https://example.com/site, the Wordpress installation folder can be placed at:

  • the root: https://example.com/wp
  • in a sub-folder of the site: https://example.com/site/wp

In summary, in order for the WP Embed Stack to work, you must insure that it complies to the following rule:

protocol://hostname:port/all must match.

So if you set your site domain is: https://example.com, then your Wordpress has to be set to the same domain and protocol. If for example, your Wordpress is set to https://www.example.com it will not work, as it breaks the rule above.

REQUIREMENTS:


Stacks 4 or above
Rapidweaver 8.x
WordPress (installed at same site/domain)

RECOMMENDATIONS:

For a seamless experience the headers and footers of the Wordpress site theme should be disabled. Some themes have that option available at the theme customizer in the Wordpress dashboard.

I recommend the BLOCKSY theme, as it's free and very customizable, without the need to edit it by hand. You can easily turn off the headers and footers, customize the fonts, layout and buttons to match your Rapidweaver site design.

ADDITIONAL NOTES:

  • Search: Wordpress search will work in the WP Embed Stack, and the results will show in the same frame where you started the search.
  • Links: links in Wordpress will work without modification, and by default will display in the same frame. However, links referring to URL's outside Wordpress must specify the parent of the frame. Just add target="_parent"to the link element. For example a link that navigates another page in your RW project, would need the target attribute.
  • Buttons: same as links, if they are linking to anything in the WP site, they need no modification. However if referring to something outside of the Wordpress content, the should also have the target="_parent" added to the link.
  • SEO: since everything in the Wordpress site has a unique URL, as you can directly navigate to everything embed with the WP Embed Stack, as such that content should be indexable. Additionally, the bots should also crawl and read the URL referred to in the the body of the RW page to which the frame is pulling the content from.

Stack Options

WP install in site sub-folder?
Check this option if your installation is as follows:
  • site installation: example.com
  • wp installation: example.com/wp
  • site installation: example.com/site
  • wp installation: example.com/site/wp
Uncheck this option if your installation is as follows:
  • site installation: example.com/site
  • wp installation: example.com/wp
Wordpress folder:
Name of folder where Wordpress is installed (only folder name)
Type:
Select the type of WP content: page, single post, all posts from a category.
Slug:
Enter the slug name for the WP page, single post or a category
Width:
Enter the width and units of the embedded content. Leave 100% for a fluid design.
Auto height to WP content:
Leave it selected is you would like for the stack to automatically adjust its height depending on the content served by Wordpress.

Uncheck it to enter a fixed height (useful when displaying content of a known height)
Enable lazy loading?
Specifies whether a browser should load an content immediately or to defer loading of the content until some conditions are met
Referrer policy?
Specifies which referrer information to send when fetching the WP content
Stacks Image 12
© Copyright 2018-2019 - All rights reserved.

This website uses cookies. By continuing to browse the website you agree to our terms & conditions and to our privacy policy.