Strange Issue with LG Member List (Latest Version)
Development and Programming
Tricky one this - is driving me mad…can’t help feeling I’m missing something obvious but been up all night and not feeling too sharp!! I have a weblog which shows a photo of a member and their name as well as some other details which are not affected. Ie:
{exp:weblog:entries weblog="{segment_3}" limit="1" category="67"}
<a href="http://{path=en/profile}{proj_leader_pic}">{photo_url}</a>
<h1><a href="http://{path=en/profile}{proj_leader_pic}">{proj_leader_name}</a></h1>
{/exp:weblog:entries}The field {proj_leader_pic} in 2nd line above draws the member ID from the LG Member list extension and as you can see appends a member ID such as 55 (say) to the link so it can be clicked and go to a Member Profile Page.
The weblog itself is defined by {segment_3} which, depending on segment, shows on of 5 different weblogs which each then show a different photo and associated ID supplied by LG Member List.
LGML supplies the correct ID in all cases but in some of them (seemingly randomly - that’s the weird bit) it inserts a tag. That is to say, the output (for a couple only) is correctly:
<a href="http://www.siteunderdiscussion.com/en/profile/142">Image Link</a>Whereas for others it wraps the ID number in a tag like so:
/profile/142Obviously with the insertion of a tag the link to the Profile page breaks…
So my question is: how is this possible given that there is no formatting possible for LGML in the custom field set-up AND it works fine with some and not others on the same template????
To sum up: 5 entries in a weblog using the same categories but differing only in choice of member from LGML drop-down - on 2 is inserted and on 3 not. On the ones where is inserted if I change the Member in the drop-down to one where it works on the others it is still Fubar.
Anyone run into anything similar?
Could this article possibly be connected?
Seems weird that it works on some of the entries but then not others but I would definitely say apply the field formatting extension fix to it as I know for a fact that I had to do that very same thing to the same extension a while back to stop some weird things from happening. Not the same as you are seeing here but it definitely doesn’t harm to update it to be correct and hopefully it will stop the headaches.
Could it have been that you had that custom field as something else at one point? If so then the field formatting for those entries may have been set to something else which caused them to work or not work and then when you changed it to use the extension the opposite happened maybe?
Hope you get it sorted soon though.
Best wishes,
Mark
Hey Mark - you’re fast!!
I was thinking the same thing, I may have used the fields previously before I found LGML as a solution - it seems like the only variable it could possibly be as there don’t seem to be any other parameters that could be affecting it.
It seems to happen randomly too now I notice - ie one that had the insert no longer has it and I have not done anything to change it. just refreshed the page a few times. Doesn’t work on the others though unfortunately.
I’ll try this fix and see what happens…thanks for speedy reply and your input!
Hey Mark - you’re fast!!
I have been known to be faster than that though, having a bit of an off day today 😉
I was thinking the same thing, I may have used the fields previously before I found LGML as a solution - it seems like the only variable it could possibly be as there don’t seem to be any other parameters that could be affecting it.
Yep it’s usually the way. Can happen with normal built-in fields too if you forget to click the check box at the bottom of the field formatting page if you decide to change it.
It seems to happen randomly too now I notice - ie one that had the insert no longer has it and I have not done anything to change it. just refreshed the page a few times. Doesn’t work on the others though unfortunately.
Hmm that’s strange as I would have expected it to stay the same no matter what you do. Refreshing the page and it changes seems a little weird to me but hopefully that extension fix will get it sorted. If not then we will have to look at other avenues.
I’ll try this fix and see what happens…thanks for speedy reply and your input!
No problems. Let us know how it goes.
Best wishes,
Mark
Umm….I was wrong about the refreshing thing, wishful thinking combined with vacuous inattention!! It didn’t fix one of them, not sure why I thought it did…
Anyway, joy! I made a new LGML field on each of them and it works now - I had used that field to try to achieve the functionality before I found LG’s extension so it must have been retaining the formatting and unable to change it once it was transmuted into an LGML field…
Thanks for the tip-off on that one! Have a virtual drink on me!! Or a real one if you are ever out this way…
Back to work!!
Thanks for the tip-off on that one! Have a virtual drink on me!! Or a real one if you are ever out this way…
No problem. I would still suggest applying the fix to the extension though as I’m pretty sure it doesn’t set the correct field formatting so you may very well run into other problems further on down the line.
Glad it’s all working for you now though. Does indeed sound like you had mixed field formats on your entries there.
Best wishes,
Mark