Not working again

Anonymous

#51846

I’m starting to lose the will to live… after not looking at the search bars for a while since updating to your latest version, I started working my way through pages looking for missing links, changing images and testing search bars.

I have 2 S&F filter bars. I found that only one bar works, on one cpt, but the second does not.

Quite simply, when I use the defective filter bar, no matter what I search for, and no matter what page I did the search from, I am returned to the cpt archive page where all posts are displayed as if nothing had been searched for. The dropdowns and meta boxes show correct post counts on both the working and defective bar. I compared the settings for both forms; identical other than the cpt and taxonomies they are filtering. I checked the cpt and taxonomies were correctly typed – they were, which I expected given that the dropdowns show correct post counts. I compared the cpt archive pages; identical with respect S&F and php. I deleted the defective form and recreated it, making no difference at all.

It doesn’t matter what I do, one just won’t work. I’ll add a private post under this. As there’s no way to add attachments or images, I’ll give you an admin login so you can see for yourself.

Can you give me any idea why this would happen?

Anonymous

#51849

This reply has been marked as private.

Trevor

#51859

This must be something to do with the way these CPT’s have been made (by hand coding?).

Having said that, normally the safest method to use with Avada is the shortcode method. In effect, you did the forms like that because you put the form shortcode in. But, in the cattax-layout.php and the vettax-layout.php (where I would have maybe expected it to be) there is no sign of the results shortcode?

Anonymous

#51862

I used the post archive option so didn’t see there was a need for a shortcode for results. It works 100% for vets, but not catteries, with the same code. What’s more, it used to work until recently.

In any event, if I have the search bar (as I would need to) on 80-90 UK county taxonomy pages for both vets and catteries (180+ pages) what page would the result shortcode go on anyway?

Each county taxonomy page exists for a reason; they are going to have to be landing pages to which existing county-only html websites will be redirected. As it stands, at least with vets, when you land on the county page it already shows the correct postcode areas and towns to choose from. So, you land on ‘kent’ and drill down to whatever town or postcode district.

But anyway, this was how it was set up originally when you took a look two months ago, and also when you looked after I added the latest version. It shouldn’t just stop working for one cpt and not for another?

Yes the cpts and taxonomies were added as via plugin, hand done. They’re identical. I even copied them today, pasted them into notepad++ and compared them. Aside from field names, they were identical.

That aside, even on the search bar that doesn’t work, it still shows the right post counts for counties, postcode areas and towns. Where the search bar is on a county taxonomy page it shows the correct post count for towns and postcodes for that county too. So if there was an error in the taxonomies or cpt setup.

Anonymous

#51863

Hit the wrong key…
So if there was an error in the taxonomies or cpt setup, that wouldn’t be the case would it?

Anonymous

#51909

I’ve been looking at this again this morning.
I compared the archive page for both post types, compared the template file they call to output posts, compared the S&F settings and then opened the plugin which creates the CPTs and taxonomies. I compared them side by side in notepad++ and went so far as swapping field names between the forms – so that if there was a difference that wasn’t a file name, it would still show as being different.

There is no difference whatsoever between the cpts, taxonomies or template files other than field names – which exist and work properly, as the taxomony pages themselves illustrate.

Rather than just delete the plugin and try another approach to displaying the posts, I tried the shortcode approach, following the instructions from your docs pages. I can see that it would require loads more work to get the results to output in the same style as already exists.

Thing is, I’m wary of getting caught up in more work when I have no idea why in the current setup, one cpt search works properly and the other doesn’t work at all. There’s no logic to it.

There must be a reason and it’s not some silly typo or similar in the templates.

Trevor

#51930

There must be a reason and it’s not some silly typo or similar in the templates.

That’s what I thought.

Anonymous

#51939

But you looked, so you can see what I mean. One form works, one doesn’t, yet there are no differences. As the cpt creation was in a plugin, you can even see that, in addition to the templates. Could you see anything that might cause one to work and one not?

If I can’t fix this, to be honest, I’m just going to have to remove the plugin and revise the site to run without a search and filter function. I need something that’s maintenance-free, and at the moment it’s not.

There are currently 1500 posts to filter, but at least I can partially do it with taxonomy-term pages, and this will probably increase to around 4000 posts over the next year (based on what has gone before). A site with manual post navigation is better than something that I can’t be sure will work. I’m just running out of ideas here.

Anonymous

#51942

I generally use firefox for testing and browsing in general, and that hadn’t shown any errors, but today I looked at console on chrome and it spat out these 2 lines:

GET http://www.britishcatteries.co.uk/cattery/ 403 (Forbidden)
Navigated to http://www.britishcatteries.co.uk/cattery/

The page opens correctly, even if strangely slow. So I’m not sure what is forbidden…
It doesn’t appear to exist for the vet cpt page.

I’ve not seen it before and it’s obviously not a normal 403 otherwise the page wouldn’t open. What would cause it, do you know?

My currently bog-standard htaccess contains only this:

AddHandler php5-fastcgi .php
Action php5-fastcgi /cgi-bin/php5.fcgi

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /cats/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /cats/index.php [L]
</IfModule>

Anonymous

#51946

Okay, now it’s working.
I asked my host company to tell me if they could trace the cause and they just replied saying they had ‘adjusted a few things’ and now it works. But I’m buggered if I know why.

[Author]

Posts