June 27, 2017 at 8:42 am #130322
Thank you again for this great plugin. We really enjoy it.
We have run into a small problem with one of your post types though and we could use your insight.
You should still have login access to this site from your previous help.
We have used the cornerstone builder to setup a test landing page on our site. The builder has been cleared for the landing page post type.
We are able to create the page in the builder as well as preview it and save it without a problem.
However, when we view the page online the cornerstone content is missing.
Here is the test landing page: https://mercury.one/go/test-lp/
You can see the content is missing, but if you edit the page you’ll see the content is clearly input in the cornerstone tab.
We thought perhaps it was an error in the landing page template, so we tried with a blank template and utilized the_content() call, but received empty content again.
We haven’t run into the problem on any other post-type or with any other plugin, so we went to you first instead of the builder dev, though we’re happy to reach out to them too if needed. But to my eye this seems like something is amiss in the landing page post type, or something we’re not aware of is happening in the back end – perhaps with the AB testing?
Thank you very much for your help.
JoshuaJune 27, 2017 at 10:22 pm #130335
Thanks for the encouraging words! Our reviews section for our free plugins could use some updated attention it hardly ever gets any! https://wordpress.org/support/plugin/landing-pages/reviews/?filter=5
Off the top of my head without digging in I am not sure. It could be filter priority conflict between landing pages and cornerstone.
I’d try, inside the template, to use echo get_the_content($post->ID) instead of the_content().
That may provide an as-is solution. Let me know what you find out. If that doesn’t work I’d be happy to take a look. Paste your link privately and I’ll check to see if my access is in place.
HudsonJune 28, 2017 at 7:25 am #130340June 28, 2017 at 7:40 am #130343June 28, 2017 at 6:54 pm #130354This reply has been marked as private.June 30, 2017 at 9:44 am #130384June 30, 2017 at 8:13 pm #130396
Thanks yes it seems I have to be authorized to test. It says you might have a reassign request in your themeco account. Would you rather me test onsite using FTP?
My installation is a local installation.July 3, 2017 at 5:41 pm #130410
Unfortunately FTP access is not an easy thing to offer with Pagely. I have invited you to the account, but you’ll have to jump through some hoops to gain access. You should have an email from Pagely to set you up and here is the Pagely support doc for access steps: https://support.pagely.com/hc/en-us/articles/203115864-Using-sFTP-on-your-VPS-Enterprise-Server
Thank you Hudson. Please be aware this is a live site.July 3, 2017 at 9:14 pm #130416
I spent a bout an hour on it today but couldn’t discover the solution in a quick enough amount of time. Is it possible to get the other developer in on the case?July 3, 2017 at 9:41 pm #130418
I hope so, I’ll reach out to them. May I pass them your email address?
BTW I have the WordPress plugin open in another tab to leave a review, right now.
Thanks!July 3, 2017 at 10:23 pm #130419
Oh cool! Inbound Now really needs more. I see about 1 every two months.
Sure you’re welcome to pass my email. Would be happy to work with them.July 3, 2017 at 10:26 pm #130420
I did though add a good foundation for editing.
I added a single-landing-page.php to the child theme and added a content-landing-page.php to /template-parts/ too and call it from the new single-landing-page.php file.
But still can’t figure out why the content isn’t showing.July 7, 2017 at 8:06 am #130468
I’m having a heck of a time getting any worthwhile support out of the builder. It appears they’ve outsourced their support and it takes 24 hours for any response and they usually kick the can as best they are able. So after a week I haven’t made any progress with them.
I’ve been poking around trying my best and it occurs to me that the landing pages definitely used to work with this builder.
Have you had any updates in the past, let’s say 1-2 months, to the LPs that might have contributed to the incompatibility? I realize that isn’t much to go on, but it might help narrow things down.
JoshuaJuly 7, 2017 at 1:43 pm #130473
It’s a timely one to narrow down.
Here you can jump back in time. If you narrow it down I can pinpoint the changes and determine a solution. I am fairly confident.July 12, 2017 at 6:54 am #130524
I have a response from the Cornerstone developers.
I’ll paste it in full below.
I can verify all of these, but one thing for sure, cornerstone utilizes the the_content() which is standard for WordPress. Which only means, that your landing page or template doesn’t utilize the same the_content(), or perhaps, the output from the_content() is completely replaced by your landing page, or the shortcodes are stripped out.
I’m not sure how cornerstone should be setup other than the_content(), it’s because it’s the standard of all post types.
And upon investigation, the InboundPro uses its own editor (other than WordPress’s standard editor) and it varies on each landing page template. Example, if you choose “Svbtle” template, it will then display two types of editor.
It will be the conversion content and the main content editor.
If you choose “Current Theme Template”, it will then display just the conversion content since the template is just a form.
In summary, you can’t use cornerstone with that setup because it’s only tied up and integrated into WordPress’s default editor and integrated to the_content() as output. Unless they are going to change their template and output its content through the_content().
You must be logged in to reply to this topic.