Jump to content
Holiday Closure, Support Availability Notice

Hump Day: 4.6 Beta 2 is live!

This topic contains 34 posts. A summary containing the most significant posts is available
View summary
Jordan Miller
Jordan Miller
in Invision Community Insider

Featured Replies

I think I spotted and SEO bug.  If you go to a url:

https://invisioncommunity.com/forums/topic/461972-xyz

the real money is the "461972".  IPB treats that as gold so even if a topic is renamed it just redirects you to the latest url/topic.  So if you type in https://invisioncommunity.com/forums/topic/461972-xyz2323232 it would redirect to the latest furl for the topic.

Here is the issue.  Take this topic.  The old behavior was if I change the name/furl for this topic to:

https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-NOTLIVE

it would redirect correctly to:

https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-live

But now it redirects to:

https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-live/?ct=1622349311

Which for whatever reason includes the current unixtimestamp. Odd.  And it splits SEO rankings up (dilutes = bad).

The canonical isn't wrong, upon source inspection (https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-live/).  But why ever add the unix time stamp?

 

 

Well for me unfortunately many things are broken, even badges for some reasons are huge and cant get them fixed so I will have to revert the changes. I assume one of the plugins or 3rd party apps are causing it. Also all the apps and plugins showing me errors when trying to click on the Marketplace in app and plugin area. 

  • Management
 

I think I spotted and SEO bug.  If you go to a url:

https://invisioncommunity.com/forums/topic/461972-xyz

the real money is the "461972".  IPB treats that as gold so even if a topic is renamed it just redirects you to the latest url/topic.  So if you type in https://invisioncommunity.com/forums/topic/461972-xyz2323232 it would redirect to the latest furl for the topic.

Here is the issue.  Take this topic.  The old behavior was if I change the name/furl for this topic to:

https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-NOTLIVE

it would redirect correctly to:

https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-live

But now it redirects to:

https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-live/?ct=1622349311

Which for whatever reason includes the current unixtimestamp. Odd.  And it splits SEO rankings up (dilutes = bad).

The canonical isn't wrong, upon source inspection (https://invisioncommunity.com/forums/topic/461972-hump-day-46-beta-2-is-live/).  But why ever add the unix time stamp?

 

 

That is a cache bust key unique to you. Normal browsing would not see that but since you are doing something "odd" it is putting that in to ensure you are not seeing a cached page.

    Upgraded our test site. Only got a handful of users on it, but alas the achievements seems to be rather greedy.

    1601133500% (32022670/2)

    The  Rebuild achievements rule nexus_Subscription is just running and running. As it's a test site there is no support, but I can't find a way to stop this job from running. I've disabled achievements but it still gets picked up on the cron job and spins the server load up. Only a test server, but still would like to kill this job. I'm sure there used to be a bugs board or something on here too. 

    I opted into the new achievements during the upgrade. I'd prefer not to delete all the rules as I was hoping to explore the new achievements. 

    Anyone got an ideas?

     

     

    Can we now use versions later than 7.6.0 of elasticsearch?

    Last one is 7.13.0, but it won't work with IPS 4.5.

     

    Upgraded our test site. Only got a handful of users on it, but alas the achievements seems to be rather greedy.

    1601133500% (32022670/2)

    The  Rebuild achievements rule nexus_Subscription is just running and running.

    I currently have a ticket in for this for another site. I believe it's a bug as it froze while manually running the task. Double check with IPS so they can look into this, in case you have the same issue.

    Edited by Dean_

     

    Upgraded our test site. Only got a handful of users on it, but alas the achievements seems to be rather greedy.

    1601133500% (32022670/2)

    The  Rebuild achievements rule nexus_Subscription is just running and running. As it's a test site there is no support, but I can't find a way to stop this job from running. I've disabled achievements but it still gets picked up on the cron job and spins the server load up. Only a test server, but still would like to kill this job. I'm sure there used to be a bugs board or something on here too. 

    I opted into the new achievements during the upgrade. I'd prefer not to delete all the rules as I was hoping to explore the new achievements. 

    Anyone got an ideas?

     

     

    Try with new beta 3 now

    Go to topic listing

    Recently Browsing 0

    • No registered users viewing this page.