
Posts posted by opentype
-
-
-
Database fields are fixed (except image uploads). For more complex situations, you can combine multiple databases and link between them, e.g. a book database which links to multiple authors for one book record. The downside is that there is no proper workflow to add this data at once. One would have to go through the databases in reverse to have the data available to link to it.
-
I moved my files on 4.7.20 to Backblaze in preparation for the upcoming "just one storage location" rule.
Seems to work fine for CSS/images and so on but NOT for the Downloads app. All file download requests end up with:
{ "code": "unauthorized", "message": "b2ContentDisposition is prohibited for unauthenticated requests", "status": 401 }
The browser URL looks like this:
https://f003.backblazeb2.com/file/[bucketname]/monthly_2025_02/musterblaetter_zip.c06ba9ff7d05c1738a669f55f55d181c?b2ContentDisposition=attachment%3B+filename%3D%22musterblaetter.zip%22&b2Expires=Tue%2C+11+Mar+2025+13%3A37%3A10+GMT&b2ContentType=application%2Fzip
-
-
4 minutes ago, Como said: Thanks for the suggestion, OT. But how would that allow members to choose two subscription plans, one (and only one) from each product line?
I don’t know the specifics about your products, so it’s hard to judge what the best options would be (regarding the use of primary or secondary groups), but as I said, you can change member groups with each purchase and then set what is allowed to purchase from that new group on the product level. So, if a regular member can purchase A1, A2, A3, that purchase can move them to a group "already has A", which has no option to buy any A product anymore (as set in the three A products). That’s the general idea. Combining multiple product line would also work with this idea, but the matrix of options and member groups can get complicated quickly with every additional product line.
-
3 minutes ago, Como said: Is there a way to have multiple product/subscription lines, ensuring that members can purchase a maximum of one subscription plan from each product line?
There is no direct logic to do any of that. But you can assign member groups with the different subscriptions and then use the member group to allow or disallow other products (including subscriptions).
-
Is there a documentation about these options? What is required/suggested/not suggested?
The Backblaze ACP links don’t work, as reported earlier.
-
-
24 minutes ago, Andreas Kwetkus said: Any thoughts, suggestions as to the benefits of Commerce, or just go with the Club's bank offering to keep it simple.
The advantage would be that the process would be mostly automated and you can offer a variety of payments options at the same time, handled all in one place. And you can tie the payment directly to the functionality within the community suite. A payment changes the member group and with that, gives access to certain areas or the entire site, while not paying automatically removes benefits.
The downside might be that the subscriptions in Commerce can only run from the day the are being purchases. If your club uses memberships based on a calendar year (which it sounds like), that is not supported at all in Commerce.
So, long story short, don’t use Commerce just a way to make a payment. It really only makes sense if Commerce is the only place to handle all membership fees and if the site makes direct use of the membership status in terms of the functionality offered.
-
25 minutes ago, My Sharona said: Something along the lines of @opentype 's SuperDocs would be a great add. I want to upgrade one of my other sites to v5 but I depend on that app quite a bit.
IPS kinda did that already. The 5.x templates now have a header image (like my templates), category images (which my templates supported) and a navigation widget (like SuperDocs). Of course it’s not identical, but pretty close.
-
-
-
-
-
-
Your summation sounds reasonable. If you don’t see clear benefits, just wait and don’t upgrade. Over time, the calculation will change. The risks become fewer as 5.x will mature and staying on 4.x will eventually become more risky with software that becomes more and more outdated and eventually not even getting security updates.
-
-
-
-
Edited by opentype
5 minutes ago, hpcrazy said: the " subscription " application which is currently marked as " outdated "
Where do you see that?
Invision Community’s payment app is called Commerce and it handles subscriptions and “product subscription“. None of them are going away. What is going away in Commerce is support tickets and physical products.
-
2 minutes ago, Sakisan said: I was directed here from the last update as a place to discuss it …
Sure. For clarifications and finding alternatives. It is indeed way too late to protest the removal.
For the future: Follow the Deprecation Tracker. https://invisioncommunity.com/deprecation-tracker/As you can see, this feature removal was announced almost two years ago.
-
17 hours ago, Matt said: Same steps as above, the JS is:
I think that needs an additional condition to only show for members, doesn’t it?
-
Edited by opentype
21 minutes ago, Marco Junior said: but try to look at it with different eyes, as I am doing.
But you’re not doing that. You are just saying, you didn’t notice any problems with it, so you declare that there is no problem to begin with. That’s not how that works.
It very much depends on the age and type of community. On my bigger and older communities, I get hundreds of bounced emails every time I send out a newsletter, even though I clean up bounces instantly. So, it’s just a fact that I have thousands, if not tens of thousands of users per community with discarded email addresses – with hundreds more each month. You stating that people don’t use inactive addresses during registration doesn’t change that many people go through many email addresses quickly, especially to sign up on websites. In some areas of the world, this seems to be common practice.
And by the way: Pointing to all the improvements in 5.x is irrelevant. If there are 100 improvements and one problem, we can still talk about that one problem and possible solutions to it. Suggesting we shouldn’t because there are also good things is a logical fallacy.
-
51 minutes ago, Adlago said: Yes, most of my pages are manual HTML. They were probably converted during the update and that broke the database connection.
How does the manual HTML look like? Something complex or just these old manual database calls?
51 minutes ago, Adlago said: How can I convert them beforehand?
You could delete the page and create a Page Builder page instead, but I think that shouldn’t be necessary. I would think that IPS should be able to detect and deal with this scenario to convert it automatically.
Changing Maximum Uploaded File Size
in General Questions
That’s what thumbnail images are for.