February 28, 2019 at 2:50 pm #134658
Not sure if this changes anything but with elementor you can do inline css or external file for each page.
Attachments:March 1, 2019 at 3:44 pm #134664
I did some more work to the asset.
Try this new asset and also try inlining the CSS. I could see how cached CSS for one variation could cause issues with the other. Inlining should keep everything together.
Attachments:March 3, 2019 at 12:30 pm #134673
Still doesn’t seem to be working.
When I add a second variant it replaces the content on both the 1st and 2nd variant with whatever content I load for the 2nd variant.
Then the CSS doesn’t work on the 2nd variant as well.March 4, 2019 at 8:36 pm #134687
I’m showing good experience with already created variations:
The thing is, if you create a new variation it won’t have any CSS applied, you’ll have to build the variation from scratch, but my tests are showing that once it’s built it sticks, and the CSS is applied.
I added a third variation after the tests in the video above and it did not overwrite A or B, though C had no CSS applied.
Did you end up disabling caching for Elementor?March 5, 2019 at 11:38 am #134694
OK whats the next step then?
I disabled my SWIFT performance plugin and put cloudflare in development mode.March 5, 2019 at 2:50 pm #134695
If your experience is still differing from mine, I could test onsite if you set me up with a lp to knock around.March 6, 2019 at 2:59 am #134697This reply has been marked as private.March 6, 2019 at 1:17 pm #134699
I can probably fix up the internal editor link.
I’ll add to to the todo(added the feature into my dev files).
For some reason when I disable inline CSS inside Elementor Settings and enable External file it seems to turn the CSS on.
This is proving hard to figure out. May have to go back to Elementor support for help. Will you check it when external file CSS is enabled?March 6, 2019 at 2:28 pm #134700
I can see that external file is enabled on my site (assume you did that) but the CSS still doesn’t seem to load for me on variants 2 or 3.
Feel free to test and enable/disable settings.
Happy to buy another premium support block to get this finished.March 7, 2019 at 4:08 pm #134706
I’ve updated the GitHub issue. I spend a few more hours on it and still can’t determine how to store and retrieve in the CSS in a custom way. Happy to take a donation once a solution is found though, thanks for offering!March 7, 2019 at 6:55 pm #134711
OK great – yeah Elementor is taking over the page builder market so having integration working 100% would make your solution really powerful.
You could sell it as a premium integration as well as no other plugins offer what you do, in terms of visitor and conversion tracking, split testing multiple pages with one central URL etc.
Lets hope the elementor guys come back with something useful.March 7, 2019 at 6:58 pm #134712
As a side note, the visitor counter seems to count a visit every time I open the editor – when I start a new page it might rack up 10+ page views just from opening the editor, checking live page etc.
Would be cool if it didn’t count visitors/conversions for users logged in.March 8, 2019 at 2:05 pm #134717
Ah it’s tracking the previews. Try turning off admin tracking in the Inbound Pro settings and it should fix it.
I hope they come back too.
I have plans to rebuild this model in a way that’s more friendly to all page builders.
Inbound Now may be close to being retired. Doesn’t make enough money, model needs to be updated, financial structure issues on the partnership side makes it a sinking ship. Pretty soon I may be forced to let it sink despite it’s good qualities.March 8, 2019 at 2:28 pm #134720
OK – I guess this begs the question – should I be integrating the Landing Pages plugin into my business if you’re going to be shutting it down soon?
Like I said – I think the Landing page system with the way variants are handled, easy split testing is really valuable for marketers.
Maybe that could be released as its own premium plugin?March 8, 2019 at 3:23 pm #134723
Landing Pages as an asset itself is pretty solid. You’re fine to use it. Many people will. I won’t dump Inbound PRO subscribers either. I may just close down support and push support to premium outlets, and reduce the price heavily to reflect this change and invite subscription holders to move over to the new offering for savings (with the same understanding that newcomers will have about future development and available support) But I won’t archive the asset totally.
When I rebuild it will be under a different brand, and a completely new, superior asset with a better, cleaner, more sophisticated approach to split testing and page building. When that time comes, you’ll probably want to switch your business over to the newer model. But a rebuild will take close to 1000 hours so we’re not due to see one until 2020.
I think it’s good to recognize the shortcomings of this outfit while you make use of it’s available assets.
You must be logged in to reply to this topic.