The following code is basically from the Module docs (I should not that in the docs the exp:weblog:entries tag does not have a closing slash in it). Anyway - it doesn’t show the flag options when it outputs. I’m wondering what I’m doing wrong?
{exp:weblog:entries weblog="feedgrab" }
<h2>{feed-description}</h2>
{exp:diggie:info entry_id="{entry_id}"} <h4>Vote for this Entry</h4> <ul> {diggie:flags} <li><a href="{path=">{diggie:flag_label}</a></li> {/diggie:flags} </ul> {/exp:diggie:info}
{/exp:weblog:entries}
So it looks something like this:
Feed description here
Vote for this Entry
UPDATE:
In testing this above, I’m getting around the above issues of not having the flag link show up just by hard coding in a +1 and -1 link but I noticed that in doing so the Flag messages in my vote template that confirms the action with a flag message is also not outputing “Your vote is +1” but the vote is being counted.
I should not that in the docs the exp:weblog:entries tag does not have a closing slash in it
Thank you… fixed
rob - 13 June 2009 10:44 PM
The following code is basically from the Module docs (I should not that in the docs the exp:weblog:entries tag does not have a closing slash in it). Anyway - it doesn’t show the flag options when it outputs. I’m wondering what I’m doing wrong?
Hi Rob,
Is this on a single entry page, or on a list view page?
As in, are you displaying 1 entry, or several?
rob - 13 June 2009 10:44 PM
UPDATE:
In testing this above, I’m getting around the above issues of not having the flag link show up just by hard coding in a +1 and -1 link but I noticed that in doing so the Flag messages in my vote template that confirms the action with a flag message is also not outputing “Your vote is +1” but the vote is being counted.
If you are to manually hardcode this area, you should be using the Flag ID or short name, NOT a value
Is this on a single entry page, or on a list view page?
As in, are you displaying 1 entry, or several?
I tried both ways. Adding an entry ID into the URL for a single entry page and without for a list view. Ideally, I’d like to utilize a list view but I tried both and no luck.
If you are to manually hardcode this area, you should be using the Flag ID or short name, NOT a value
Agreed and have been using the flag ID numbers for testing and those votes are counted in the CP but no flag message is outputed in my success/failure template.
I tried both ways. Adding an entry ID into the URL for a single entry page and without for a list view. Ideally, I’d like to utilize a list view but I tried both and no luck.
K, I think there’s an issue with the version of Diggie… I will check back with you very shortly…
rob - 15 June 2009 10:42 AM
Agreed and have been using the flag ID numbers for testing and those votes are counted in the CP but no flag message is outputed in my success/failure template.
Another issue with Diggie. We noticed that the {if diggie:message} conditional stopped working in 1.0.1. If you remove it from around the {diggie:message} variable, you should be fine
Another issue with Diggie. We noticed that the {if diggie:message} conditional stopped working in 1.0.1. If you remove it from around the {diggie:message} variable, you should be fine
Great - I can confirm that this message on the success/failure template does work for me after pulling out the conditional.
So, I was thinking I could just hard code in the flag values and not use
{diggie:flags}
to provide the links and then go from there. But,I noticed that when I was testing this - while logged out - I could vote an unlimited number of times. I have set the preference for 1 vote per use in the CP.
I assume with the
{diggie:flags}
code working that this code might prevent unregistered visitors from voting multiple times? When I was logged in, I was restricted to voting just once as expected.
I should note that I was interested in seeing if I could have unregistered visitors vote and limit them also to just one vote. It would be great to have the option to not have to force a visitor to register just to vote up and down if it was possible to restrict but IP and cookie like one would do for a poll.
So, I was thinking I could just hard code in the flag values and not use
{diggie:flags}
to provide the links and then go from there.
Yeah, that works too…
rob - 18 June 2009 04:38 PM
But,I noticed that when I was testing this - while logged out - I could vote an unlimited number of times. I have set the preference for 1 vote per use in the CP.
Yes, this is currently a known issue and we have it corrected for a near future release
The issue currently only happens to Guests/Non logged in members.
rob - 18 June 2009 04:38 PM
I assume with the
{diggie:flags}
code working that this code might prevent unregistered visitors from voting multiple times? When I was logged in, I was restricted to voting just once as expected.
Nope… has nothing to do with Diggie:Flags
Only to do with the Diggie:Vote function
rob - 18 June 2009 04:38 PM
I should note that I was interested in seeing if I could have unregistered visitors vote and limit them also to just one vote. It would be great to have the option to not have to force a visitor to register just to vote up and down if it was possible to restrict but IP and cookie like one would do for a poll.
As I mentioned above, this will be available within the next couple days… we have it set to restrict based on IP address
Ok, great - glad to hear about the non-logged in ability when fixed. Thanks for the update, I appreciate it. If you can, would you please let me know if you forgo releasing this new version for any reason. I am in development on a small website for work and the diggie function is one of two main purposes of functionality on the site and will be standing by until it’s available.
