Posts by hus_hmd

If you are on standard Perch, you will also need to add the following at the bottom of the page:

You may also need to hold the redirects to see the debug message like so:

Do you get any errors? You can check your error log or enable Perch debug mode.

And have you added your PayPal config to perch/config/shop.php?

You need to call perch_shop_checkout() before outputting any HTML or whitespace to the page. In fact, you don't need to output anything. You either redirect to PayPal or perhaps back to the cart or payment confirmation page. This is, more or less, all you need on the page:

The above only relies on the user being a logged in member before redirecting them to PayPal. You can perform further checks like checking whether the cart has items and/or requiring a form (single button) to be submitted from the previous page.

How are you initiating the PayPal checkout? Can you share your master page where you do this?

This is how related items data is fetched. If you need the related item's data, you'll need to fetch that separately.

perch_collection() behaves the same way. However, inside a template the perch:related tags fetches the related items (and renders the content) for you. When you add fields inside a perch:related these are only used for output. It makes no difference to how Perch saves the data.

So you'd use something like this:

Blocks would be the way to go. You'd set up a single content region to manage the blocks. The editors will be able to add/remove/reorder blocks as they wish.

What does the error message say?

Hi,

I don't think Perch ships with the language packs. You need to download it. This is the German translation.

Place the file in /perch/addons/plugins/editors/redactor/langs/.

In /perch/addons/plugins/editors/config.js, specify the language and load the translation file:

Generally the perch_pages_navigation() function is what you'd use to get other pages data. What are you hoping to achieve? Would you like to pass this data to a content region?

Hi Tony,

A possible option could be to skip the templating when you fetch the items, reverse the array and then render the template with perch_template():

Quote from nascent

I'm not aware of any CMS solution that charges a fee so if a project ends, why wouldn't a license owner want to re-purpose or re-sell their license?

There is nothing stopping you from reassigning older licenses to new projects. I'm not sure whether the license agreement even prohibits you from doing so.

As for reselling a license, the license terms do not allow that. You purchase a license to use the product. You are granted permission to use the product. The third-party to which you would resell the license would not have permission to use the product, which is fair.

The proposed license model sounds like it would continue to allow customers to reassign licenses to different projects. That's what many customers do anyway. Perch didn't suggest they'd stop this. However, this time they're not going to give free updates forever. You get 1 year's worth of updates. If you need more (perhaps it's an ongoing project or you're reusing a license after an old project dies and now need the latest version), you pay for another year's worth of updates. It's a fair model to both parties.

Quote from nascent

How do you actually reuse a license anyway?

I was under the impression that when you specify a domain in your account, that unless the license matched your domain wouldn't work.

You can reassign the license to a different domain. This normally happens when one an old project dies or stops using Perch, so the owner of the license reassigns the license to a new domain for a new project instead of purchasing a new license. It is perhaps worth noting that v2 licenses get a free upgrade to v3, which means people have been reusing old v2 licenses for new projects on v3.

This reminds me of Chris Ferdinandi's post: Running a trust-based business. Now that Perch has communicated how the reuse of old licenses hurts them I wonder whether people will continue reusing old licenses for new projects.

It looks like you are using Mollie as your payment gateway. If you implemented the integration yourself, are you calling the finalize_as_paid() function on successful orders?

Quote from hus_hmd

it is also important to recognise that it is your responsibility as the developer to make sure you run the software in a compatible environment. In order to achieve this, you now know you can roll back to PHP 7.3.

Hi Charlie,

This blog post may help: Understanding Custom Editors Config

Hi Mike,

Quote from Mxkert

I also don't see anything about the tag in the debug after the purchase.

Nonetheless, could you share the debug message you get after the purchase?

Happy to help!

Yes, you'd be able to use clean URLs. You would set up a route to the page (Pages > your page > location tab).

Your route in this case would be (no slash at the start):

slug is the type of value the URL segment represents. s is what you are naming this URL segment (so you can use it on the page). You can get the value of this segment with perch_get() just like you would with URL query parameter.

Hi,

perch_item_index does not give you a unique ID. It gives you the number of the item in a list in whatever context it is (number of item in a region, number of item in a repeater, etc). So I would prepend the region unique ID to avoid possible clashes.

You can use _id which is the unique ID of the region. And you can use the scope-parent attribute on the repeater tag to make the content from outside the repeater available inside it:

Hi James,

This is the expected behaviour. You need to pass the slug dynamically.

If your URL is something like /products?s=example-product, you can use perch_get() to get the value of the URL query parameter s: