You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am pulling a feed from the following URL: http://voicesfromjapan.blogspot.com/feeds/posts/default?alt=json-in-script which contains string ($) characters as the names of fields. For instance, in the object that returns, the text for the title is in the feed.entry.title.$t field. When I put "title.$t" in my template, the field doesn't get rendered. If I use "title.type" (another field in title), it is rendered. I'm assuming this issue has to do with the $ in the title as it is messing up the regex that replaces the text--is that a safe assumption? I would try to fix it myself; however, I'm not that great with regular expressions.
The text was updated successfully, but these errors were encountered:
Hi thanks for reporting this. Yes that would be the issue. I'm close to wrapping up 1.5 so I'll have a look at this for you ASAP and let you know how it goes.
I think I figured out how to get it to work. In the replaceVariables method I changed the regEx to the following: /{{[ ]?([A-Za-z0-9$.[]]?)([ ]?|[ ]?._?)?[ ]?}}/g
Of course this would need to be fully tested, but so far, so good!
Great, glad you worked around it. That seems like the correct solution, I'll just have to change it in a couple of other places to make sure works throughout. Thanks for the fix!!!
I am pulling a feed from the following URL: http://voicesfromjapan.blogspot.com/feeds/posts/default?alt=json-in-script which contains string ($) characters as the names of fields. For instance, in the object that returns, the text for the title is in the feed.entry.title.$t field. When I put "title.$t" in my template, the field doesn't get rendered. If I use "title.type" (another field in title), it is rendered. I'm assuming this issue has to do with the $ in the title as it is messing up the regex that replaces the text--is that a safe assumption? I would try to fix it myself; however, I'm not that great with regular expressions.
The text was updated successfully, but these errors were encountered: