Larry Kachadorian

Update button now showing in AdminCP ... ran it,  and version is now correct

As mentioned elsewhere in other discussions regarding Achievements, certain communities are populated with  'older' members who tend to be put off by competitive points, ranks , ever changing badges etc.  But they can appreciate being discretely recognized for their longevity of association with the site. 
And yes, the join date is shown, but I'd like the ability to directly highlight longevity.  I've tried various methods to achieve this with the current default features in Achievements but can't produce what's needed.  I came close, but the text still said "Rank: or Current Rank" which is not desired ... and none of the rule options truly fit, so it was manual which isn't at all workable.
I'd like a plug in to extend the existing, default feature shown below

Seems to me the existing logic simply compares  the joined date to 'now' and based on "x" amount of time differential displays the symbol and hover text
I'd like to add more conditions to that logic:
If time between joined date and now is >= 5 years and < 10 years, display new symbol with text "5 + year member" If time between joined date and now is >= 10 years and < 15 years, display new symbol with text "10 + year member" If time between joined date and now is >= 15 years and < 20 years, display new symbol with text "15 + year member" If time between joined date and now is >= 20 years display new symbol with text "20 + year member" And yes we do have members with 20+ years
This would be applied automatically and would not need an option to apply manually per member
This would be accessed via ACP only and would not need to filter by group as this would apply to all groups since its "self adjusting" and relevant regardless of group.
Other features:
Although my example logic is fixed (for ease of demonstration of use case) a more logical capability would be to the ability to add steps based on any time difference - like a yearly increase rather than 5. ability to add custom hover text for individual steps  ability to upload a custom "symbol" for individual steps (although if that adds unnecessary complexity - good with a single symbol across all steps, TBD)  actual placement of symbol TBD (although if that adds unnecessary complexity - good with existing) Thanks
 
 

@Mark H  So, the issue here is a 63% increase in cost ($30 to $49) for no additional value given our use case.  
Is there no chance then that Invision might at least entertain  a unique cost option with unique restrictions that would insure minimal impact to the cloud environment ... you can see our minimal usage at https://sportbmw.ipbhost.com/

@Mark H  So, the issue here is a 63% increase in cost ($30 to $49) for no additional value given our use case.  
Is there no chance then that Invision might at least entertain  a unique cost option with unique restrictions that would insure minimal impact to the cloud environment ... you can see our minimal usage at https://sportbmw.ipbhost.com/

Having a separate test/dev site separate from your "production" environment is pretty much standard practice. Yet for cloud accounts that has presented a problem ... unless we've missed something that is available.
Since transitioning to Invision cloud , in addition to our main site, we have paid for the smallest legacy cloud account as a test/dev site.  Its closed to guests , and can only be accessed by accounts that are created by our Admin.  We prototyped our site there prior to our actual migration from our previous vendor and have maintained it since. 
This second site was/is invaluable in preventing  issues  ... particularly in one of the major upgrades  (4.5 ??)  which changed how the default theme handled the header space and made some 3rd party themes as well as some apps unusable.  We were able to find out what issues specifically affected our site.  And it was huge.  If we had just applied it to production, it would have been a disaster.
Same with the initial roll-out implementation of lazy loading .  We had images imbedded in the Forum descriptions which caused issues which we caught on our test/dev site.  Invision support recognized the problem as somewhat unique to us at that time.
I could go on, but the value that a test/site provides is obvious.  Even for small, non commercial sites like ours.
However now that option is going to cost more since Invision is closing out the legacy options with new, more expensive offerings.  The increase in cost and "functionality" does not, for us, create any new value.  Particularly since our use case for the account has an infinitesimal impact on the Invision host environment. 
There should be a fixed, low cost method of providing an option for managers/developers of cloud accounts where than can duplicate their unique production environment for the purposes of testing new apps/upgrades etc.

Having a separate test/dev site separate from your "production" environment is pretty much standard practice. Yet for cloud accounts that has presented a problem ... unless we've missed something that is available.
Since transitioning to Invision cloud , in addition to our main site, we have paid for the smallest legacy cloud account as a test/dev site.  Its closed to guests , and can only be accessed by accounts that are created by our Admin.  We prototyped our site there prior to our actual migration from our previous vendor and have maintained it since. 
This second site was/is invaluable in preventing  issues  ... particularly in one of the major upgrades  (4.5 ??)  which changed how the default theme handled the header space and made some 3rd party themes as well as some apps unusable.  We were able to find out what issues specifically affected our site.  And it was huge.  If we had just applied it to production, it would have been a disaster.
Same with the initial roll-out implementation of lazy loading .  We had images imbedded in the Forum descriptions which caused issues which we caught on our test/dev site.  Invision support recognized the problem as somewhat unique to us at that time.
I could go on, but the value that a test/site provides is obvious.  Even for small, non commercial sites like ours.
However now that option is going to cost more since Invision is closing out the legacy options with new, more expensive offerings.  The increase in cost and "functionality" does not, for us, create any new value.  Particularly since our use case for the account has an infinitesimal impact on the Invision host environment. 
There should be a fixed, low cost method of providing an option for managers/developers of cloud accounts where than can duplicate their unique production environment for the purposes of testing new apps/upgrades etc.

Having a separate test/dev site separate from your "production" environment is pretty much standard practice. Yet for cloud accounts that has presented a problem ... unless we've missed something that is available.
Since transitioning to Invision cloud , in addition to our main site, we have paid for the smallest legacy cloud account as a test/dev site.  Its closed to guests , and can only be accessed by accounts that are created by our Admin.  We prototyped our site there prior to our actual migration from our previous vendor and have maintained it since. 
This second site was/is invaluable in preventing  issues  ... particularly in one of the major upgrades  (4.5 ??)  which changed how the default theme handled the header space and made some 3rd party themes as well as some apps unusable.  We were able to find out what issues specifically affected our site.  And it was huge.  If we had just applied it to production, it would have been a disaster.
Same with the initial roll-out implementation of lazy loading .  We had images imbedded in the Forum descriptions which caused issues which we caught on our test/dev site.  Invision support recognized the problem as somewhat unique to us at that time.
I could go on, but the value that a test/site provides is obvious.  Even for small, non commercial sites like ours.
However now that option is going to cost more since Invision is closing out the legacy options with new, more expensive offerings.  The increase in cost and "functionality" does not, for us, create any new value.  Particularly since our use case for the account has an infinitesimal impact on the Invision host environment. 
There should be a fixed, low cost method of providing an option for managers/developers of cloud accounts where than can duplicate their unique production environment for the purposes of testing new apps/upgrades etc.

Having a separate test/dev site separate from your "production" environment is pretty much standard practice. Yet for cloud accounts that has presented a problem ... unless we've missed something that is available.
Since transitioning to Invision cloud , in addition to our main site, we have paid for the smallest legacy cloud account as a test/dev site.  Its closed to guests , and can only be accessed by accounts that are created by our Admin.  We prototyped our site there prior to our actual migration from our previous vendor and have maintained it since. 
This second site was/is invaluable in preventing  issues  ... particularly in one of the major upgrades  (4.5 ??)  which changed how the default theme handled the header space and made some 3rd party themes as well as some apps unusable.  We were able to find out what issues specifically affected our site.  And it was huge.  If we had just applied it to production, it would have been a disaster.
Same with the initial roll-out implementation of lazy loading .  We had images imbedded in the Forum descriptions which caused issues which we caught on our test/dev site.  Invision support recognized the problem as somewhat unique to us at that time.
I could go on, but the value that a test/site provides is obvious.  Even for small, non commercial sites like ours.
However now that option is going to cost more since Invision is closing out the legacy options with new, more expensive offerings.  The increase in cost and "functionality" does not, for us, create any new value.  Particularly since our use case for the account has an infinitesimal impact on the Invision host environment. 
There should be a fixed, low cost method of providing an option for managers/developers of cloud accounts where than can duplicate their unique production environment for the purposes of testing new apps/upgrades etc.

Having a separate test/dev site separate from your "production" environment is pretty much standard practice. Yet for cloud accounts that has presented a problem ... unless we've missed something that is available.
Since transitioning to Invision cloud , in addition to our main site, we have paid for the smallest legacy cloud account as a test/dev site.  Its closed to guests , and can only be accessed by accounts that are created by our Admin.  We prototyped our site there prior to our actual migration from our previous vendor and have maintained it since. 
This second site was/is invaluable in preventing  issues  ... particularly in one of the major upgrades  (4.5 ??)  which changed how the default theme handled the header space and made some 3rd party themes as well as some apps unusable.  We were able to find out what issues specifically affected our site.  And it was huge.  If we had just applied it to production, it would have been a disaster.
Same with the initial roll-out implementation of lazy loading .  We had images imbedded in the Forum descriptions which caused issues which we caught on our test/dev site.  Invision support recognized the problem as somewhat unique to us at that time.
I could go on, but the value that a test/site provides is obvious.  Even for small, non commercial sites like ours.
However now that option is going to cost more since Invision is closing out the legacy options with new, more expensive offerings.  The increase in cost and "functionality" does not, for us, create any new value.  Particularly since our use case for the account has an infinitesimal impact on the Invision host environment. 
There should be a fixed, low cost method of providing an option for managers/developers of cloud accounts where than can duplicate their unique production environment for the purposes of testing new apps/upgrades etc.

Did the final migration to the 4.6 version today ... movement of all the old data and settings went flawlessly .... 
New product is great .   No issues at all !!

Thank you very much for the relatively "instant" action on making ignore forum and ignore topic 4.6 compatible !!!!!
This has made our migration to 4.6 now possible.

No problem ... when you get to it is fine.

Hi
brand new instance of the cloud based version created today
downloaded and installed faq today
I created Categories in the AdminCP
I created several Q&A in the front end and saved each
When creating each Q&A the saved result appear as expected under their respective categories
However …
When leaving the FAQ page and then re-accessing via the normal menu tab nothing shows, not even the categories
Only the "Submit Q & A" button shows
And yet if I add another Q@A all previous categories and entries appear
In the ModeratorCP the last entry on the menu says :
F.A.Q
faq_faq_pl