Hamada Hussein

Hello,
It does not make sense to combine 2 plugins which do the same thing!
You need to choose only one of the two plugins.
Woocommerce is a super great plugin for almost any products website including tours and travel.
Wp travel engine is only tours.
I used wp travel engine for a few weeks and then had to switch to woocommerce because with every wp travel engine update, technical problems appear!
My personal feeling:
The two major tours plugins wp travel is one of them) are a modified version from woocommerce.
I recommend using only woocommerce for your tours/travel website, you will only need to modify the language file to make it fit to your niche.

I hide most of the taxonomies from search engines, and I use pages instead and map the links properly to redirect to each taxonomy, this way I can avoid most of the nonsense archive and taxonomy pages that I can not control, but I do this with around 95% of the content, and around 5% left as is, because I just can not use page instead of it, like the search results page.

Thank you for your reply. Indeed, the word “trips” is not in my permalinks, I use the word “Tours” for trip base permalink, and I have no idea where this ” Trips page come from”!!
Also, thank you for the CSS code, but it hides all descriptions of all taxonomies which is something deferent than what I mentioned in my question.
I think the “Trips” word is the title of the search results page!! If you please point me where I should look to modify this and change the word Trips, and also add the proper description to it.
Thanks.

So, you are telling me to diable the Trip Inquiry until I see the update available?

https://egyptfuntours.com/Egypt-tours-packages/?itinerary_types=&price=&min_price=1723&max_price=2257&view_mode=grid

This problem is really annoying me, and it is not a theme-related! When a user uses the search filter to find trips, the search page also shows the word “Trips” as a title and under it the word ” description ” and that is it. This is extremely bad as a user experience, and also negatively affects SEO. Please I need suggestions on how to solve this?

Every time an update is released, I put my hands on my heart!

I know I can show activities, travel keywords, & trip types, through the menu, but still, you did not answer my clear question. If each category/tag is like a page or apost, we would be able to add headers/cover/or any block type.

• This reply was modified 4 years, 8 months ago by Hamada Hussein.

@wensolutionsupport,
Thanks for the reply. You did not get me right, I mean the other way around, I want to add a block (any html code) at the bottom of a category page under the “related trips”, like showing a contact form or a CTA.

Hello @wensolutionsupport,
Thank you so much for your reply. It did the trick. Thanks so much.

(SOLVED) Here is the code that worked with me:
#primary .post{
width: 50%;
padding: 0 30px;
}
#primary .site-main{
display: flex;
flex-wrap: wrap;
margin: 0 -30px;
}
#primary .post .entry-footer .meta-holder {
margin-top: 16px;
}
@media screen and (max-width: 768px){
.blog #primary .post{
width: 100%;
padding: 0 20px;
}
}

Are you sure you are talking about wp travel engine, or it is another plugin, wp travel?

Hi All,
Thank you for the update, it fixed the problems, however, I detected another small problem with the navigation primary menu and I am not sure if it is related to the plugin or to the Travel agency theme! the children of the dropdown menu are not responsive when hover, the browser expands and you will have to scroll side wide to see the children items, which is not logically possible as it automatically disappears when you move the mouse. You will need to create a menu item with children in the far right end of the menu and hover over it.
This happens with layout 5 in the Travel agency.
Also, it is all because the dropdown menu goes by default to the right side!

• This reply was modified 4 years, 10 months ago by Hamada Hussein. Reason: adding more info

When I use the inspect tool, it seems that the blog style is controlled by #primary .post, that is the only one affecting the style, but it also affects the post itself.

Now the code is in my additional css