Posts by hus_hmd

Hi Stephen,

This is an array of strings:

This is a single string:

You need to use an array:

I realise it is not what you're looking for; it wasn't meant to be the solution. I'm hinting quite badly for you to test every step so you'd figure out what is not working. As things stand, it sounds like the filtering on perch_blog_custom() is not working as expected.

If you do get a URL from perch_layout_var('url'), copy one and hardcode it:

This is just to confirm that the filtering works.

While this is perhaps not a huge number, you'd be calling perch_shop_product_variants() for each product (so 13 times). This is probably going to make the page slower than it should be.

If you don't have too many products, you can fetch all products and their variants, then render them using pipit_template() (from the Pipit app) - which works in a similar way to perch_template(), but supports pagination.

If you have a large number of products, the above approach won't be great as you'd be fetching all the products for all pages (even though you're only displaying 12 per page).

Try removing the spaces between the values:

You are also missing a comma after the first filter array:

You are correct; It is for a single product only.

I don't think that's possible with perch_shop_products(); its primary use is to fetch/output parent products. Enabling the variants option only includes them per product so they are not taken into account in pagination.

If you are only listing the variants for a single product, you should be able to output a paginated list with perch_shop_product_variants()

Hi,

How are you outputting the variants? Are you using <perch:variants></perch:variants>?

Mxkert is probably the easiest option. However, filtering inside the template may lead to some issues. If you need pagination, the number of results per page may be inconsistent (and some pages may not show any results). The other issue is you can't easily tell when you get no results.

An alternative would be to skip the templating, disable pagination and handle the rest in PHP:

You may find these blog posts relevant:

• Content Search
• Restrict content search to a single Collection
• Grouping search results

Hi Paul,

It sounds like you are using the Perch Forms app. If you navigate to the Forms app in the control panel and then go to the form in question, you should see the received responses. Do the responses display the received data?

I meant to output it on its own like so:

If you have debug mode turned on, you can output it to the debug message instead:

Ultimately, you need the variable to hold the correct postURL value.

Quote from dosa

UPDATE: it's working, but because I hidden a variable in testing on the 'blog_search_result.php" page to this:

If you remove the filtering, you probably won't get the expected result. If things are working fine up to the layout stage, the next step would be looking into whether the layout variable is holding the expected value. Try outputting it:

Do you get the result URL as expected?

Hi James,

You can use the manual gateway for this: https://docs.grabaperch.com/addons/shop/gateways/manual/

Hi Grant,

It looks like you do not need to skip the templating. You can have the rendered template to be returned instead of output like so:

If you don't need the template to re-evaluated at runtime, you can use perch_content() instead:

I'd check things one by one until you find where it is not working.

(1) Turn on debug mode and check for errors

(2) Your search template is only set up to show results from the Blog app. If you get a result from another source it will output an empty <li></li>. Does the term test return any Blog results? You can restrict the search to the Blog app:

(3) Check what you're getting what expect. Output the result_url and/or showall the available variables. Is it a blog post URL like you expect?

If you are only dealing with a small number of values, the replace attribute is also an option. You can flip the order of the values in the options attribute:

If you use Apple and Round Orange as the value, you can use the urlify attribute to output URL friendly versions apple and round-orange. Alternatively, you can use the format attribute to convert the text to all lowercase or all uppercase.

And there's also the CSS route:

As far as I know Perch Shop doesn't let you set a default address for customers at the moment. So you'd need to set the address for each order.

Perhaps you can set up a template for the order address form that has a hidden field with the address value and just displays a button (which can say "Next" or something like that). Visually to the user it would look like a button to go to the next step, but clicking it would also set the order address.

Hi Jack,

Quote from jack

so I can't work out why these would be calculated any differently between the cart and the final order.

Do you have multiple tax locations set up with different rates? If so, I think Shop would recalculate the tax when the customer selects their address.

As far as I know there is no runtime function to do this.

You could use the Tags class directly, just be careful when updating the app in the future. Note that your template may need to use the perch:content namespace here. And this won't get you the quantity value qty like perch_blog_tags():

If you also need the quantity, an option would be to set up your template to render the list in JSON:

And in PHP you can convert the JSON to an array, randomise the order of the array items, slice the array to the size you want and render the list with perch_template()