3

This turned out to be a bug when Tag is used with other addons that add cache variables to the Sessions object before it actually exists. A workaround for the issue will be in Tag 4.2.7, which we are testing for release.


3

You said that your problem is to make the URL's point to the right template. If you don't mind about to have 10 entries from both channels, instead of 5 of every one, you can merge the variable pair and use a conditional. {exp:tag:related_entries url_title="{segment_3}" channel="channel_A|channel_B" orderby="date" sort="desc" limit="10" paginate="bottom"} ...


3

When updating freeform, you need to delete the old directories before uploading the new: Updating: Within your sites ./system/expressionengine/third_party/ directory, delete the freeform folder and upload the new one from the /system/expressionengine/third_party/ directory in your download package. Within your sites ./themes/third_party/ directory, delete ...


2

Since your question is about the View All link setup, I removed the itinerary-vars set_list. There's no need to run your exp:tag:related_entries tag twice when you're using Stash. Let Stash do the work to cut down on db queries. {exp:stash:set_list name="itinerary_events" parse_tags="yes"} {exp:tag:related_entries channel="event" orderby=...


2

If your template group names match the short name of your channels then simply use {channel_short_name} So you could do: {exp:tag:related_entries url_title="{segment_3}" channel="channel_A|channel_B" orderby="date" sort="desc" limit="10" paginate="bottom"} <a href="{channel_short_name}/template'}">{title}</a> {/exp:tag:related_entries}


2

I think I figured it out. For anyone interested, the global footer along with the tags in the detail pages uses the websafe_separator="-" parameter, while the tag entries page (page that user lands on after they click on a tag" did not have this parameter in it. More information can be found in the docs here.


2

You'll need PHP to create first a list of entry_ids, which will then be fed to {exp:tag:tags}. Then, you will have to create a list of unique tags, which can also be done with a PHP array. Creating a list of entry_ids based on a tag First we'll need to create a list of entry_ids to pass into {exp:tag:tags}. Set PHP to Output: <?php $entry_ids = ""; ?&...


2

Simply ordering by the Low Events channel field would do the trick, so try: orderby="my_low_events_field" sort="asc"


2

Ah, Parse Order. This particular issue takes place in phase #5 of the linked PDF: parsing of module and plugin tags. This works as follows: The first {exp:-tag encountered in the template is parsed. When the tag is done, the parser starts again, parsing the first {exp:-tag it encounters then. This goes on and on until there are no more {exp:-tags left. So,...


2

If you're using tag IDs, then you can use the Cloud tag to display the names. The most important thing you'll read about Low Search is how parameters work. With that in mind, if you follow this example, then you could use this code to display the tags: {exp:low_search:filters query="{segment_3}"} {exp:tag:cloud tag_id="{low_search_tag_id}"} {tag} {...


1

Ok - the problem was trivial. As you can see in the template-code above I just missed a slash. This one {page} {pagination_url}{pagination_page_number} {page} just has to be replaced with {page} {pagination_url}{pagination_page_number} {/page} It was worked out by the excellent and engaged guy from Solspace - thanks a lot!


1

This is also issue with EE pagination, which Tag uses: if you use the same URL, eg http://example.com/entries/two+apples with pagination in {exp:channel:entries}, the pagination URL can become http://example.com/entries/two apples. Spaces in URLs render as %20 in the address bar, which is the URL entity equivalent of a space. There is possibly a way to ...


1

You could always just use the {field:tag_fieldtype_short_name} tag, which Solspace recommends in their docs. If that doesn't work you can always look at the page source after it parses and see the way Solspace requires the field. Docs for using the Tag module in channel form.


1

You could use CSS rules that override the rules applied to the Tag widget. If you don't want to use the Tag widget, you could have a simple textarea form with name="your_tag_field_name": <textarea name="your_tag_field_name"></textarea> This lets you customize the form field the way you want (eg. make it responsive). Each tag would have to be ...


1

You should be able to list entries tagged with your three tags using {exp:tag:entries} and the tag_separator="" parameter. For example: {exp:tag:entries channel="products" tag_separator="+" marker="color" } The default is a comma. If you want tags to be separated by a +, then use tag_separator="+". In some cases, depending on your server and htaccess ...


1

I'm guessing this was an issue of file corruption, or perhaps some files did not upload properly to the production server. These pages appear to be working fine after I deleted all /third_party and /themes files for the Tag module and re-uploaded them to the server. I'll keep an eye on it and will post again if anything else comes up. Thank you Solspace ...


1

Tag data should be saved to exp_channel_data, and therefore be searchable. Super Search can search Tags like this. Although I'm not sure for EE's simple_search form, I assume it would also work fine. Is the Tag field set as searchable? If not, please set it as searchable in the custom field settings in the EE CP. You may need to re-save the entry so that ...


1

You could have a look at the exp_tag_entries database table, in particular the tag_group_id column and make manual modifications, it's not recommended without having backups ready and knowing what you're doing. The best and safest way would indeed be to delete the tag in the Tag CP, then recreate it from an entry form in a Tag custom field assigned to your ...


1

You're nearly there. Just got the nested list tags the wrong way round, and you have to use the {entry_id} from the channel entries tag as the unique context when setting the list since {place_entry_id} is only available when getting the list: {exp:stash:set_list name="place-{segment_1}" parse_tags="yes" parse_depth="3" save="yes" scope="site"} {exp:...


1

The developer of DataGrab emailed me the solution. I figured I would post it here so that anyone else who may have this problem down the road is able to solve it! First, you need to update the Wordpress plugin as described in my original post. Then copy this bit of code and save it as "datagrab_tagger.php" and place inside the DataGrab "fieldtypes" folder: ...


1

DataGrab doesn't currently have support for the Tagger field type. However DataGrab does have support for Solspace Tag which may provide the correct functionality for you without having to manually update. Tag isn't free, but Solspace offer a 30-day money back guarantee so if it doesn't work you should be able to get a refund. http://www.solspace.com/...


1

One method is to check which checkboxes are checked, build a URL containing multiple tags which is recognized by Tag (see the Tag documentation about multiple tags in the URL when using {exp:tag:entries}), and redirect to this URL. Here's an example: Assuming you have these three example tag checkboxes: <input type="checkbox" name="tag[]" value="foo">...


1

The solution was to use {exp:tag:entries} to display entries associated with a tag, but also make sure the status of those entries are set to "open", and if they aren't use the status="some_other_status" parameter.


1

This solution over at Solspace support would likely fix this: http://support.solspace.com/solution/categories/115922/folders/236531/articles/145012-how-to-avoid-issues-with-the-tag-custom-field-autocomplete-not I'll post the answer here for more exposure: There may be cases when the Tag custom field's autocomplete does not display any results. First, please ...


1

Have you tried the offset="" parameter? For example, to get the next 6 related entries: {exp:tag:related_entries channel="product" entry_id="{embed:entry_id}" orderby="relevance" limit="6" offset="6"}


1

In your channel settings you have the ability to enter a channel url and a channel comment page url - and when it is filled in, it is available to you as a variable in your entries loop (normally - whether it is within the tag module I couldn't say, but it very well may be). It has the same effect as url_title_path, for example. But instead of something ...


1

If you are okay with doing a multi-step submission process, you could try a combination of manipulating the Tag:Form template tag and populating it with the Tag:Cloud template tag. http://www.solspace.com/docs/tag/form/#examples (last example as your base) {exp:tag:form form_id="my_form" return="path_to/my_template" entry_id="{entry_id}" } {...


1

If the user isn't going to create tags as part of the process, why use the Solspace Tag module at all... just use EE's native categories which you can manually add in the control panel and they can select via checkboxes.


1

I've replied to your email already, but will repeat here for visibility. In short, you want a single dropdown that contains custom fields that in turn relate to tag groups. You want to see if the selected field is not empty. The tricky part is that usually, Low Search fields will target field values, not the fields themselves. Low Search can target ...


1

I can't answer for Low Search, but you can use a query to get a list of tag groups: <select name="i_dont_know_for_low_search"> {exp:query sql="SELECT * FROM exp_tag_groups"} <option value="{tag_group_id}">{tag_group_name}</option> {/exp:query} </select> Ignoring Low Search for an instant, if you were using a regular HTML form ...


Only top voted, non community-wiki answers of a minimum length are eligible