# Contact Segment using tag working on compose Mautic instal?

**URL:** <https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972>\
**Category:** Mautic 4 Install/Upgrade Support\
**Created:** [March 9, 2022, 4:38pm UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972 "2022-03-09T16:38:26Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![techbill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/techbill/32/8325_2.png) [@techbill](https://forum.mautic.org/u/techbill)\
**Post date:** [March 9, 2022, 4:38pm UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972/1 "2022-03-09T16:38:26Z")

</div>

**Your software**  
_My PHP version is_ : 7.4+  
_My MySQL/MariaDB version is_ (delete as applicable): MySQL 5

**Updating/Installing Errors**  
_I am_ (delete as applicable): IUpdating  
_Upgrading/installing via_ (delete as applicable) : Command Line (compose install)

_These errors are showing in the installer_ : none

_These errors are showing in the Mautic log_ : none

**Your problem**  
_My problem is_ :

I created a contact segment setting tag filter then save it but when I check again, it shows filter as blank again. This was working for me before I reinstalled Mautic using compose but now after reinstalling with compose, it no longer working for me or filter is not adding contacts with the tag I wanted filtered.

_Steps I have tried to fix the problem_ :  
Cant figure why filter tag is not being saved.

---

<div class="post-metadata">

**Author:** ![techbill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/techbill/32/8325_2.png) [@techbill](https://forum.mautic.org/u/techbill)\
**Post date:** [March 9, 2022, 5:48pm UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972/2 "2022-03-09T17:48:52Z")

</div>

I recalled that whenever we create a new contact segment then go to the filter tab - after selecting a filter in the dropdown menu, the filter box should appear underneath allowing us to select any available filter correct?

I select tag but no box is appearing underneath the filter selection etc.

Something broke or maybe server missing an extension needed for compose install when I switch Mautic over to compose?

![filter](https://us1.discourse-cdn.com/flex020/uploads/mautic/original/2X/c/c96c0579f45fa7b1140d44b84ba1078290963ef0.gif)

---

<div class="post-metadata">

**Author:** ![techbill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/techbill/32/8325_2.png) [@techbill](https://forum.mautic.org/u/techbill)\
**Post date:** [March 9, 2022, 7:24pm UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972/3 "2022-03-09T19:24:54Z")

</div>

I deleted Mautic and its’ database to try again. We really haven’t started using Mautic was in the process of learning and configuring it to suit our need. But we were getting ready to put it in production until we read the announcement about composer so we decided to start fresh with composer to make it future proof for us.

It’s not looking good at all so far …

Anyway, with the new fresh install, we are still not able to set up the filter on Contact Segment to select any of the filter or “tag” which we wanted to select in the first place.

Is anyone able to select filter for Contact Segement?

---

<div class="post-metadata">

**Author:** ![techbill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/techbill/32/8325_2.png) [@techbill](https://forum.mautic.org/u/techbill)\
**Post date:** [March 9, 2022, 8:10pm UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972/4 "2022-03-09T20:10:10Z")

</div>

Got this one sorted …

The server had shell function restricted so I had to remove the restriction from the shell function since it seems that Mautic needed those shell function to work.

---

<div class="post-metadata">

**Author:** ![anotart](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/anotart/32/338_2.png) [@anotart](https://forum.mautic.org/u/anotart)\
**Post date:** [March 9, 2022, 10:34pm UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972/5 "2022-03-09T22:34:46Z")

</div>

I am having this same problem – when selecting the filter, none of the filter options appear. I just installed Mautic 4.2.0 using bitnami on AWS. All of this is new to me – was on cPanel using Mautic 3x. Couldn’t upgrade because of the database version on the hosting account.

I FINALLY figured out how to get SSH access and tried clearing the cache (again, all new to me, took hours to figure out how to get SSH access. When I tried clearing cache, I didn’t get any error messages, so I think it worked.)

I looked into the solution @techbill used. Can’t see how to do it, but it also sounds “dangerous” if you don’t know what you are doing. Would appreciate any assistance.

---

<div class="post-metadata">

**Author:** ![techbill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/techbill/32/8325_2.png) [@techbill](https://forum.mautic.org/u/techbill)\
**Post date:** [March 9, 2022, 11:11pm UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972/6 "2022-03-09T23:11:32Z")

</div>

The problem came back again with filter for me. I went home for the day.

I am going to troubleshoot it some more tomorrow to see why I am still unable to use filter in segment.

I suspect maybe I am missing some pho extension that composer mautic require to have.

I will update here if I discovered anything

---

<div class="post-metadata">

**Author:** ![techbill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/techbill/32/8325_2.png) [@techbill](https://forum.mautic.org/u/techbill)\
**Post date:** [March 9, 2022, 11:20pm UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972/7 "2022-03-09T23:20:40Z")

</div>

What db and version were you on?

---

<div class="post-metadata">

**Author:** ![anotart](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/anotart/32/338_2.png) [@anotart](https://forum.mautic.org/u/anotart)\
**Post date:** [March 10, 2022, 12:26am UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972/8 "2022-03-10T00:26:34Z")

</div>

My original install was mySQL 5.6. New Mautic versions require 5.7. Hosting provider could not give me a timeframe for updating. That also was stopping me from updating my PHP to 7.4. (My Mautic version on my hosting account was 3.2.4)… In my original Mautic install, the segment filtering worked as you would expect it to.

---

<div class="post-metadata">

**Author:** ![techbill](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/techbill/32/8325_2.png) [@techbill](https://forum.mautic.org/u/techbill)\
**Post date:** [March 14, 2022, 6:01pm UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972/9 "2022-03-14T18:01:28Z")

</div>

I fixed my issue by executing this command

php console mautic:assets:generate

---

<div class="post-metadata">

**Author:** ![lgwapnitsky](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/lgwapnitsky/32/1623_2.png) [@lgwapnitsky](https://forum.mautic.org/u/lgwapnitsky)\
**Post date:** [March 18, 2022, 1:03pm UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972/10 "2022-03-18T13:03:52Z")

</div>

I tried the asset regeneration, but am still having the same issue.

Mariadb 10.7  
Mautic 4.2.0  
PHP 7.4  
Ubuntu 20.0.4

---

<div class="post-metadata">

**Author:** ![anotart](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/anotart/32/338_2.png) [@anotart](https://forum.mautic.org/u/anotart)\
**Post date:** [April 6, 2022, 6:16pm UTC](https://forum.mautic.org/t/contact-segment-using-tag-working-on-compose-mautic-instal/22972/11 "2022-04-06T18:16:59Z")

</div>

Upgrading to 4.2.1 solved this for me
