If I share the module URL to Facebook, I get the same picture and description as if I share my profile (bio/profile pic). It doesn't use the data available in the form update/create fields of the module.
However, if i share a detail page created by the module, I get the correct data, as provided by the form create/update (see attached).
My question is, how do I get that data to be shared with the module URL http://kenrich.me/sales instead of http://kenrich.me/sales/27 (or whatever item number the profile ends up with after numerous creations/deletions/creations).
On my profile 27 is the current item_id and /sales/27 is the uri There is only one item allowed to be created by the module as the whole point is to produce one page URL for promotions that has all saleable items listed or linked.
It seems to me, there should be a way to make it so that the simplest URL, the module URL which is profile/sales carries the right share information.
When I do a debug to the detail page that shares properly I see the URL's under $post
$_post}
Array (6)
_uri => "/sales/27"
module_url => "ken-rich"
module => ""
option => "sales"
_1 => "27"
_profile_id => "1175"
The data for OG info is there under $item. This is what's missing from the item_index.tpl
sales_image => ""
sales_image_name => "Ken's Sales.png"
sales_title => "Ken's Store"
sales_text => "This is a store with products and services from Ken Rich. An ebook, CD, video..."
I'm thinking (maybe I'm nuts) that there are 3 possible scenarios to achieve the desired result (proper sharing at the module URL profile/sales).
1) Perhaps the tab and url for the module can be linked to the detail page instead of the item_index.tpl and then what is displayed and shared by the module URL (profile/sales) would be the detail page (already sharing properly).
2) Or keep the Sales tab (and module URL) linked to the item_index.tpl but alter the share tpl to use the data from the form designer create/update available at $item of the uri_1 instead of the module url.
3) Or this is something that requires modifications at the PHP level of the module and scenario 1 and 2 are not viable paths.
--
Ken Rich
indiegospel.net
updated by @ken-rich: 07/28/16 07:59:04AM