sound

Let's test that by checking the obvious possibility - edit the Administrator group, go to the Content tab and scroll down to the 'Tags' section. Is the "Can use prefixes?" setting toggled on?

Do you mean this yellow part isn't showing up?

Working fine on my 4.7.7 online and 4.7.8 Beta 2 boards.

below gives an interesting view on all this
https://web.dev/bfcache/?utm_source=lighthouse&utm_medium=lr#never-use-the-unload-event
 
Never use the unload event #
The most important way to optimize for bfcache in all browsers is to never use the unload event. Ever!
The unload event is problematic for browsers because it predates bfcache and many pages on the internet operate under the (reasonable) assumption that a page will not continue to exist after the unload event has fired. This presents a challenge because many of those pages were also built with the assumption that the unload event would fire any time a user is navigating away, which is no longer true (and hasn't been true for a long time).
So browsers are faced with a dilemma, they have to choose between something that can improve the user experience—but might also risk breaking the page.
On desktop, Chrome and Firefox have chosen to make pages ineligible for bfcache if they add an unload listener, which is less risky but also disqualifies a lot of pages. Safari will attempt to cache some pages with an unload event listener, but to reduce potential breakage it will not run the unload event when a user is navigating away, which makes the event very unreliable.

below gives an interesting view on all this
https://web.dev/bfcache/?utm_source=lighthouse&utm_medium=lr#never-use-the-unload-event
 
Never use the unload event #
The most important way to optimize for bfcache in all browsers is to never use the unload event. Ever!
The unload event is problematic for browsers because it predates bfcache and many pages on the internet operate under the (reasonable) assumption that a page will not continue to exist after the unload event has fired. This presents a challenge because many of those pages were also built with the assumption that the unload event would fire any time a user is navigating away, which is no longer true (and hasn't been true for a long time).
So browsers are faced with a dilemma, they have to choose between something that can improve the user experience—but might also risk breaking the page.
On desktop, Chrome and Firefox have chosen to make pages ineligible for bfcache if they add an unload listener, which is less risky but also disqualifies a lot of pages. Safari will attempt to cache some pages with an unload event listener, but to reduce potential breakage it will not run the unload event when a user is navigating away, which makes the event very unreliable.

below gives an interesting view on all this
https://web.dev/bfcache/?utm_source=lighthouse&utm_medium=lr#never-use-the-unload-event
 
Never use the unload event #
The most important way to optimize for bfcache in all browsers is to never use the unload event. Ever!
The unload event is problematic for browsers because it predates bfcache and many pages on the internet operate under the (reasonable) assumption that a page will not continue to exist after the unload event has fired. This presents a challenge because many of those pages were also built with the assumption that the unload event would fire any time a user is navigating away, which is no longer true (and hasn't been true for a long time).
So browsers are faced with a dilemma, they have to choose between something that can improve the user experience—but might also risk breaking the page.
On desktop, Chrome and Firefox have chosen to make pages ineligible for bfcache if they add an unload listener, which is less risky but also disqualifies a lot of pages. Safari will attempt to cache some pages with an unload event listener, but to reduce potential breakage it will not run the unload event when a user is navigating away, which makes the event very unreliable.

The issue with the strong tag will be fixed in the release. I couldn't upload a fix for that until the current version was approved, and asking them to cancel the pending version would delay the fix for the autocomplete even further.
I know permissions are a bit weird for the member markers, but this particular permission is handled in the group setting. 

 
@dhpunkt I've noted down you feature suggestion and I'll see what I can do about it.

Thanks for clarifying. I have added a bug report for this issue as I can see the problem in that scenario.

thanks for the reply Andy @Andy Millne
ok understand that working as above is fine and should be intended if you are indeed using the 'overview' as per the selected option
however if you are not using the 'overview' as the default selection, say you select the 'week view' as default then  every event will have a link that will  now send viewers to the 'month' page and the same for any calendars using  'day view'
which to someone using the week or day view as 'default' choice does bring in major usability issues along with seo  ones
 
Could you not add a 'if \IPS\Settings::i()->calendar_default_view== overview add the ?view=month ' and if not..
then leave the static url as generic so that the week, and day views choices as default are then respected and followed?
thanks
 
 

latest upgrade and for me this is still an issue
3-4 seconds without own suggested edit, normal speed with edit
 
 
 

Happy Hump Day, team! Sort of. 😔 
One of Invision Community's founding fathers, @Rikki, is amicably moving on from Invision Community to pursue another exciting opportunity. This is his last week with us. He has a few parting words to share with you:
 

Rikki has been an instrumental player in Invision Community's success; we're bummed to see him go, but at the same time excited for him to spread his wings. 
Please leave some well wishes for Rikki in the comments! 
---
Speaking of the team, @Matt Finger wrote a new dev blog post touching on the PHP8 Compatibility Scanner, our Pre-Upgrade Resource Checker and a full change log for our upcoming September release:
 
 
--- 
And last but not least, 4.7.2 Beta 1 is officially out. Check out the release notes here.
See you in the replies. 🙏 

Thank you everyone, I'm sad to be leaving but very excited for what comes next. I'm sure you'll still see me around here, just without that Staff badge.

Our mariadb slow query logs pointed to poor results when guests were viewing the new 'combined view' topic listing  (it was fine when members were viewing)
4.8 seconds + for the query below
/*xxxx::IPS\Helpers\Table\_Content::getRows:489*/ SELECT forums_topics.*, author.*, last_commenter.*, core_tags_cache.tag_cache_text FROM `ibf_forums_topics` AS `forums_topics` FORCE INDEX (last_post) LEFT JOIN `ibf_forums_forums` AS `forums_forums` ON forums_topics.forum_id=forums_forums.id LEFT JOIN `ibf_core_tags_cache` AS `core_tags_cache` ON tag_cache_key=MD5(CONCAT('forums;forums;',forums_topics.tid)) LEFT JOIN `ibf_core_members` AS `author` ON author.member_id = forums_topics.starter_id LEFT JOIN `ibf_core_members` AS `last_commenter` ON last_commenter.member_id = forums_topics.last_poster_id WHERE forums_forums.can_view_others=1 AND forums_topics.approved=1 AND forums_topics.approved!=-2 AND forums_topics.approved!=-3 AND ( NULLIF(forums_topics.moved_to, '') IS NULL ) AND forums_topics.forum_id IN(1,2,128) ORDER BY forums_topics.last_post desc LIMIT 0,50;  
this slow query appeared to be due to the effect the where clause ' forums_forums.can_view_others=1'  was having on the query, maybe index issues?
removing this clause via the getItemsWithPermissionWhere function
if ( !$member->member_id ) { /// $where[] = array( 'forums_forums.can_view_others=1' ); } resulted in a 'normal' speed listing of 0.8 seconds for guests
maybe worth a dig ?
 
 

Thanks for reporting this, I have forwarded this to @Matt who's our DB Master:)

Can add that we're seeing the same numbers. Takes 14+ seconds to load a combined view with 2 subforums. 

I asked a similar question once and was helped by the query given in this reply
 

commerce alert
monitor the invoices table so that any member with an invoice that is still pending (not paid)  after say 24/48/72 hrs  (settable option) period  gets sent an alert suggesting that they should finish the sale

It would be useful to expand the topic reporting function for user profiles as well.
Very often lately IPS Spam errs and gets numerous spammers to sign up, but it errs really often...
Even now a spammer has registered on this forum who has been following me, the report button would have been really helpful to alert you of this unwelcome user
Spammer: https://invisioncommunity.com/profile/632173-harrysng100/

@Rikki
In the view template:
{{if $event->rsvp || $address || $event->map( 270, 270 ) }} <div class='ipsColumns ipsColumns_collapsePhone'> <aside class='ipsColumn ipsColumn_wide'> <div> {template="eventSidebar" group="view" params="$event, $attendees, 'Mob', $address"} </div> </aside> <div class='ipsColumn ipsColumn_fluid'> {{endif}} Happens that the same conditions are also checked in the eventSidebar template:
{{if $address || $event->map( 250, 150 )}} and
{{if $event->rsvp }} So it won't have any issue if you remove the condition from the view template. Leaving it as the way it is today, it prevents to add something in the eventSidebar, unless the event has an address/map or is RSVPed, which can't be required/necessary in all events.
Thank you.

Perfectly summarised. Therein lies the problem. Innovation seems to have stalled with the apps but IPS is still the best and the competition is way behind; perhaps that's the problem.
We still haven't got a Reject All option in the cookie banner.
Commerce lacking PDF invoices/receipts for customers does seems outdated. I would hazard a guess that a modern e-commerce system today up (against platforms like Shopify and Magento) should offer efficient sales and inventory reporting, after all, the data is all in there, it just needs extracting and exporting.
I'm not sure how many accountants would make use of PDF invoices, wouldn't they be of more use to customers and site owners. Perhaps accounting firms and bookkeepers would benefit from CSV, XML and owners Freshbooks and Quickbooks intergration.
A lot of work clearly went into Commerce, if your dealing with peoples data and payments that is a huge reassurance in particular the payment side of it, but it's had deprecated features for some time now and like the other apps it's stagnated for years, aside from compatibility and security updates.
Going back to innovation though, given the usefulness and appeal of these apps, especially Gallery, Commerce and Pages, it's a tad bit sad, after all, there's not only the cost of the apps in the first place to consider for new users to IPS and then the never-ending rental of them.
If you want to temporarily skip a renewal, you have to buy the app all over again from scratch if you want to reactivate it. Effectively the client is caught between a rock and a hard place so I still think clients should ideally have more flexibility in terms of managing the apps, to be able to enable or disable app licences prior or near to the 6 monthly renewal, also to be able to freely move apps between licences say limited up to twice a year, rather like having displayname change limits.
If an app fails to warrant renewal on a site, and the client has multiple licences, it's surely in both the client and Invision's interests to allow the client to move it to another community licence, rather than just cancel it outright. It could do much better on a different community or as part of a brand new community project.
Or if we have a site client who no longer needs their site, we ideally have to keep the licences going ready for when and if we pick up a new client or consider starting a new personal site, as opposed to buying a brand new set of licences all over again.

Create a "listener" for Webhooks in IPS to avoid using external service like Zapier, IIFT or Integromat for Invision Community -> Invision Community Zaps. Especially for zaps where  trigger and action are in the same community.
Usage examples:
if a new user registers -> create a record in Pages if a new blog entry or gallery image is published -> create a topic if a page in database is updated -> send notifications to followers if a record is update in reciprocal database -> update the main record if a file has been update -> add a post to the file topic with change log if user purchases a product -> join him to club and so on  

Storefront
Sell merchandise and other physical items to your clients or fans.
Orders
Track all paid, pending or cancelled orders in one place.
 
https://invisioncommunity.com/features/commerce/
 
 

2022, Invision Community Powered by Shopify
 
that footer could be a game changer for me
 
 
 

promoted by the recent seo improvements post 
a suggestion
if when recording the 'last_poster_name' username in the 'forum_topics' table,  invision also recorded at the same time the id # of the actual 'lastpost' in a new column
 could the many "&do=getLastComment" redirects then  be  replaced with a direct url link ? 
eg
forums/topic/463744-seo-suggestion-removal-of-dogetlastcomment/?tab=comments#comment-2869177
 
 
 
 

Ok, I've added an issue in our tracker to restrict the JS to just Nexus.

Arne,
I agree, you don't need to be a conspiracy enthusiast or tin foil hat wearing website owner to see it's grossly invasive of privacy and quite unjustifiable in the days of GDPR. We can't restrict it to commerce or checkout related pages only and Stripe bless 'em, surely can't detect card fraud by 100's if not 1000's of updates about individuals reading topics about say favourite pizza toppings, looking after tropical fish etc.
When you factor in more or highly sensitive content, perhaps medical conditions or preferences, thats really not good, off the scale not good!
Site visitors can't opt out of it, certainly before it starts tracking them, as far as I can see, which isn't right.
There have been numerous topics here about it in the past. Its only a recommendation but certainly not a requirement, so I wish IPS (as established corporate advocates of anonymous posting and pride etc) would step up and take some ownership on improving this, and provide us with AdminCP options either for sidewide, commerce or checkout Stripe integration only.