Posts by Mxkert

I am not really sure how to do that.

Quote

"You normally only want to index fields that you need to filter and/or sort by. The more fields you index, the more likely your queries going to be slower (though this depends on other factors too)."

As taken from this article from Hussein. I believe it should also work for products.

Are you indexing all the fields in the product template? You can use the no-index attribute on the fields you don't have to index. I'm not sure if this will solve your problem but you could always try.

When you turn on debug, by placing define('PERCH_DEBUG', true); in the /perch/config/config.php file, and outputting the debug on the bottom of your page, you can see exactly which template is being used.

perch_blog_author_for_post(); uses the /perch/templates/blog/author.html template.

perch_blog_post(perch_get('s')); uses the /perch/templates/blog/post.html template.

perch_blog_post_categories(perch_get('s')); uses the /perch/templates/blog/post_category_link.html template.

You can always create your own template and use it. For the blog post, you have to use perch_blog_custom as follows:

You could turn on debug and check what error message is thrown on the bottom of the screen.

Can't you set the product's status to inactive instead of deleting it?

This should be fairly easy to accomplish.

Loudon The problem with this solution is that this will be overwritten if you would later on update the blog app (you will overwrite those files)

Another option is to change the itemTitle in the database in the perch3_menu_items table.

I would suggest using one template to edit the content in perch (for example: edit.html) and then a different template to display it on your website (for example: display.html)

Your repeater is now at the bottom of the page, so in a display.html you could put it somewhere else, without interfering with the editting template.

Does your display template have the repeater at the bottom?

I guess you would have to create a tiny app which loops through all tags applied to logged in member.

perch_member_remove_tag($tag) does indeed require a tag as an argument.

You can use:

as follows:

Does it work with only the redirect line, without the rest of the code?

What does the debug output look like?

When editting this region, you can click on region options (on top) scroll down and choose a (different) template.

You can use the filter option to show every post except the post with the current post slug, like this:

Could you enable debug and post your debug script from that page here?

Hello,

Is there a function or another way to check if discount code is set?

Mike