Allegheny

Hi Ehren,
Thanks for checking.  I did find the problem in my custom css.  I went back and cleared my custom css again and started adding things back line by line and finally found an incorrect z-index assigned to the ipsLayout_header.  Corrected that and now all is good.  Not sure how I missed that before.
Sorry, for the trouble and thanks for confirming that it was not a return of the original issue.
-Chris

I'm unable to reproduce the issue on the default theme on either 4.6.8 or 4.6.9. I tried checking your site, however I'm unable to access it as a guest.

I just wanted to offer that I am running Invision Community v4.6.7, invite system v2.6.2 and SMTP for email and everything just works great.  My community is running under the default theme and the server is running PHP v7.4.24.
I sent out a couple of invites yesterday, users received emails fine and registered without issue.
I don't mean to interfere and will leave the diagnostics to Adriano and Dean.  I just wanted to offer that my default installation is working and thought the working specs might help narrow down the issue Dean is experiencing.
 

I just wanted to offer that I am running Invision Community v4.6.7, invite system v2.6.2 and SMTP for email and everything just works great.  My community is running under the default theme and the server is running PHP v7.4.24.
I sent out a couple of invites yesterday, users received emails fine and registered without issue.
I don't mean to interfere and will leave the diagnostics to Adriano and Dean.  I just wanted to offer that my default installation is working and thought the working specs might help narrow down the issue Dean is experiencing.
 

Thank you for reporting, and I have added this to our internal bug tracker to be resolved

Thanks!  Outstanding and fast support as always.
Your dedication and professionalism is seriously appreciated!

I can confirm this. I will fix when I have to update the app.
In the meantime, you can run the following query in your PHPMyAdmin (or in the SQL Toolbox):
alter table staffappsystem_fields engine = 'InnoDB';  

I am just curious and am not experiencing any issues right now, but have discovered that "one" of the database tables in the Staff Application System is not using the server's default InnoDB engine - all other's show InnoDB.
The table in question is "staffappsystem_fields" which is using MyISAM.
I am not sure why this is as I've always used "InnoDB" as the default on this server and all other db tables in the db are InnoDB as they should be.  So, I am assuming the Staff App System installation imported / created this table using MyISAM for some reason.
This outlying table flagged as a informational warning by the "support tool".
Again... I don't see an issue right now but am wondering down the road the headaches this might cause.
 

It goes without saying that we all want every one of  the marketplace apps to be updated within days of a new release.  We need to better manage our expectations as Adriano has a very large collection of marketplace and custom apps that he supports. They will all be updated when they get updated and not a moment sooner.  
Coding and testing works best when you are in a good frame of mind.  Being constantly pestered for updates is unlikely to put Adriano in such a state.  Be of good cheer@Adriano Fariaand the other marketplace developers, we appreciate all of you...

Oh hell. 😄
Ok, just submitted a fix. I'll contact marketplace moderators to see if it goes live soon as it was just a language bit and controller moving to another module.
Thanks.

I agree!  Most users are not going to find the "search by tags" link under the advanced search form which kinda makes tags useless in these regards.

All's good with my install as well.

Thank you. I’ll take a look when I have to upgrade the app. 👍

Hi Adriano,
This is not a big deal, just a pesky cosmetic thing... but I thought I'd let you know.
On the landing page for tutorials (v2.5.2) if you hover your mouse over the description of any tutorial (not the picture) you get a link balloon popup that repeats the words of the description including the html code.  See attached.

Yeah... I've done a complete reversal on this after thinking on it for several hours.
I should have paused and given it some more thought before only seeing it as a negative.  This new change will work just fine.
Thanks for the positive reinforcement, it's appreciated.

Ok.... I've played with it some and I see the setting is "persistent" and that's a little better.  At first, I was thinking you'd have to login in publicly each and every time and then go to account settings... yada yada yada... Which would have been a nightmare.
I guess this is the end of switching visibility around as I know I'll never remember to turn visibility back on under this new scheme.

So... they have to login "publicly" and fully visible to all; then navigate to account settings and hide themselves?  I am sorry, but that makes zero since to me.  Granted.... having the ability in the account settings is nice for those that need to switch to annoyance  while already signed in.... but, for those of us who like to just log in quickly to do or check something and then leave without anyone noticing we are there...  that option is now gone.  And, people will see us before we ever make it to account settings to hide ourselves.
One step forward... three steps back.

Thanks Adriano!

Thank you. Just submitted a new version to fix the upgrade. It should be out soon.
Follow the file to get notified when IPS review and approve it. 👍

Yeah... I've done a complete reversal on this after thinking on it for several hours.
I should have paused and given it some more thought before only seeing it as a negative.  This new change will work just fine.
Thanks for the positive reinforcement, it's appreciated.

Yeah... I've done a complete reversal on this after thinking on it for several hours.
I should have paused and given it some more thought before only seeing it as a negative.  This new change will work just fine.
Thanks for the positive reinforcement, it's appreciated.

So... they have to login "publicly" and fully visible to all; then navigate to account settings and hide themselves?  I am sorry, but that makes zero since to me.  Granted.... having the ability in the account settings is nice for those that need to switch to annoyance  while already signed in.... but, for those of us who like to just log in quickly to do or check something and then leave without anyone noticing we are there...  that option is now gone.  And, people will see us before we ever make it to account settings to hide ourselves.
One step forward... three steps back.

Yeah... I've done a complete reversal on this after thinking on it for several hours.
I should have paused and given it some more thought before only seeing it as a negative.  This new change will work just fine.
Thanks for the positive reinforcement, it's appreciated.

It’s better because it’s an account feature now which means your state will be the same in any device you use to access the community. You don’t need to worry if you’re anonymous in your phone but not in your laptop, etc.