Devin Humbert

Tom, it looks like your site is using the “Zingiri Web Shop” plugin. I’ve never even heard of it, so I can’t help. I would check out their support:

https://www.zingiri.com/support/

Devin

Hi Tom,

This topic is related to the “RecipePress” plugin. It seems you are talking about an e-commerce plugin? Which plugin are you having trouble with?

Hi bobA1,

I’m part of the effort to keep RecipePress alive and updated, and if you have time I’d love to hear your ideas for how we could make it better. You can just reply here if you’re able to.

Thanks!
Devin

Hi awakegal,

I’m part of the effort to keep RecipePress alive, and while I agree the documentation needs work, I was hoping you could talk a bit more about your problems integrating the plugin into your theme, what you’d like to see, etc.

Thanks!
Devin

We’ve added a setting for enabling/disabling pluralization and singularization of ingredients and serving sizes. It will be included in the next update (coming soon), but for now you can get it by checking out the plugin from SVN here:

https://code.google.com/p/recipe-press/source/checkout

Devin

Sure – (edit: removed email address)

Can you give me your site URL so I can look at it?

Can you backup that file (so you don’t lose the changes), and then replace everything in it with what’s below (kind of the “default” WordPress .htaccess)?

# BEGIN WordPress

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Can you post the contents of your .htaccess file? It should be in the WordPress root directory.

It looks like your host uses cPanel – do you know how to access cPanel? I think it’s typically https://yourdomain.com/cpanel or https://yourdomain.com:2082.

Once logged in to cPanel, look for the Logs or Logging section, and the Error log. Before clicking it, try to do whatever it was that caused the 500 error to show up first, to make sure the error is captured.

Then paste the error log here.

OK, here is something I’ve tested, and I think it will work for your purposes.

In .htaccess, replace what I gave you earlier with:
RewriteRule ^search/(.+)$ index.php?s=$1&search=true [L]
“search/” can be replaced with whatever you want the alias to be, so it could be something like this:
RewriteRule ^whatever-search/(.+)$ index.php?s=$1&search=true [L]
or
RewriteRule ^life-universe-everything/(.+)$ index.php?s=$1&search=true [L]
So for those, you would access, respectively:
domain.com/whatever-search/some-search-term
and
domain.com/life-universe-everything/some-search-term

Does that make sense? OK, that’s only half of it. In functions.php, located in your theme directory (wp-content/themes/your theme name/functions.php), put the following code at the bottom:

/**
 * This, in conjunction with a rule in .htaccess,
 * enables us to have a "pretty" search URL (like example.com/search/hello-world).
 */
add_action('init', 'replace_plus_signs_for_search');
function replace_plus_signs_for_search()
{
	// search=true is set in the .htaccess rewrite rule, to make things simpler.
	if (array_key_exists('search', $_GET) && $_GET['search'] == 'true')
	{
		// if a search term is defined
		if (array_key_exists('s', $_GET))
		{
			// replace dashes with a plus
			$_GET['s'] = str_replace('-', ' ', $_GET['s']);
		}
	}
}

So now, if you link to https://example.com/life-universe-everything/this-is-a-term, it will take you to the search results for “this is a term”.

Hope that helps.

Ah, I see. I found it in the normal WP forums, I didn’t see anything about the CPT archive plugin.

When getting a 500 error, the only way to really figure it out is to look in the Apache error logs. Do you know how to access those? If not, who is your hosting provider?

I think I made a poor choice of words.

Rewrite rules are not redirection – or at least, not necessarily. They “rewrite” – so in the example I gave above, the address for the page is “blah.com/search/blah”, but (behind the scenes), the user is actually (unknowingly) accessing index.php?s=blah. It’s totally invisible from an end-user point of view.

So if you added that rule, you could link to domain.com/search/blah, and it would show the search results page for the term “blah”.

So that rule basically tells your webserver:

“People are going to be visiting the URL domain.com/search/blah. That file doesn’t exist, but let’s show them index.php?q=blah – WITHOUT them knowing.”

It seems to me that’s what you want, but maybe I still don’t understand…

All you need is a rewrite rule in .htaccess. Add the following on the line after “RewriteBase /”:

RewriteRule ^search/(.*)$ index.php?s=$1

That transforms https://blah.com/search/blah into index.php?s=blah.