There are a few options – a common one would be to add the beacon to a qa / uat site and test there. However, what if the content isn’t as up-to-date – is there another solution?
The approach below is a bit hacky so don’t rely on this for your final integration testing! However, on the plus side, it’s very quick to see things in action 🙂
- Select the site you want to test on. Nominally: www.sitecore.net
- Fire up a new instance of Sitecore on your dev machine (8.1 if possible) with the host: fxm.www.sitecore.net
- Create a new FXM site entry and set the host to be fxm.www.sitecore.net
- Note, we will change this later
- Through the FXM experience editor add a hello world placeholder and control to your page
- This should create you an item in the tree under: ‘/sitecore/system/Marketing Control Panel/FXM/www sitecore net’
- Open up the new placeholder you added in the tree and note the selector. This can be anything you want – for the sitecore site update this to be say ‘#Form1 > div.shell’ (without the ‘s)
- To find the value to use, dive into chrome developer tools, right click the element you want and choose ‘copy XPath’ or ‘copy CSS path’ – I found css was easier to work with as you can target specific elements, not array entries
- Update the primary domain entry added in step 3 to be www.sitecore.net
- Publish the lot
- Visit www.sitecore.net in a browser and note nothing has changed
- In the chrome console run the following script:
- If the script here fails, make sure the ‘ are proper single quotes, not funky curly ones.
- You should see in the network tab a new request to the beacon – the response should be json containing all the data needed for rendering your changes to the page
- Check the page – in theory anything set in step 4/5 should now be applied to the page
A word of caution – if you are interested in how the placeholders work you can always view: Presentation details -> Final renderings. However be careful, don’t ok (ie save) once you’ve reviewed them as the format saved back into the field isn’t compatible with FXM.