Lindy

I'm sorry for your frustration. I've gone ahead and done this for you as a courtesy one last time, but unfortunately, the IPS retail system and the Marketplace are two different entities - the funds are not commingled. Doing this compromises the accounting on both ends, so the best way to do this moving forward would be to withdrawal the credit from the Marketplace and submit it to the client area as a normal payment. 
I apologize for any inconvenience this may cause and thank you for your understanding and cooperation. 

I truly appreciate the fresh perspective and positive energy you brought to us, Jordan. I wish you the very best in your future endeavors and have no doubt that you will carry that ++ vibe wherever you go. 🙂 
You are certainly leaving a void, however, I'm hopeful you'll continue to check in, let us know how you are doing and sprinkle some of that magic Jordust™ that the community has come to love and appreciate. 
Best of luck! 🙏

Thanks so much, Lindy! Appreciate our time together. Lots of Jordust™ to share

I truly appreciate the fresh perspective and positive energy you brought to us, Jordan. I wish you the very best in your future endeavors and have no doubt that you will carry that ++ vibe wherever you go. 🙂 
You are certainly leaving a void, however, I'm hopeful you'll continue to check in, let us know how you are doing and sprinkle some of that magic Jordust™ that the community has come to love and appreciate. 
Best of luck! 🙏

I truly appreciate the fresh perspective and positive energy you brought to us, Jordan. I wish you the very best in your future endeavors and have no doubt that you will carry that ++ vibe wherever you go. 🙂 
You are certainly leaving a void, however, I'm hopeful you'll continue to check in, let us know how you are doing and sprinkle some of that magic Jordust™ that the community has come to love and appreciate. 
Best of luck! 🙏

I truly appreciate the fresh perspective and positive energy you brought to us, Jordan. I wish you the very best in your future endeavors and have no doubt that you will carry that ++ vibe wherever you go. 🙂 
You are certainly leaving a void, however, I'm hopeful you'll continue to check in, let us know how you are doing and sprinkle some of that magic Jordust™ that the community has come to love and appreciate. 
Best of luck! 🙏

You cannot export passwords.  Even the IPB software itself does not know what the password stored in the database is.... the password itself is hashed hashed and salted in a unique way per community that is stored in the DB.  That value is them compared to what is entered by the user when the same salt/hash is done again.   So just taking an encrypted password would not work as you would also have to understand how the password was hashed and salted uniquely to simply compare a password.  
To be honest, you're better off just having the password set a new password via email verification on first login.  

It doesn't solve the data privacy issue and I'd rather put energy into APIs to make it easier to integrate with third party apps and code.

Honestly, I'm not entirely comfortable with the idea of third parties directly executing SQL queries on customer databases. If it all goes wrong, we have to dig out back-ups to fix it. This is not a slight on anyone's abilities, I've deleted an entire table of customer tickets with a mistyped query. It happens.
We are not going to create a system where third parties have access to the client databases. There is no audit trail for what actions were taken. When our team need to access a cloud site, we complete a reason form which is stored to form part of an audit trail so we know exactly what was accessed and why. We also have to access via a fixed IP address VPN so there is a data trail.
We take our cloud customer's security and data very seriously.
The SQL toolbox should have been removed a decade ago in all honesty. As we move forward with our cloud platform, more and more SQL tables will be stored centrally and not exposed to the client in any case, meaning admins won't have access to all the data the community uses which could case a lot of confusion.

(Edited later to add:)
In terms of what to do with debugging, I do sympathise. I generally made prodigious use of the simple \IPS\Log::log( json_encode( $data ), 'argh_send_help' ); logger. I have also in the past used \IPS\Db::i()->select(...); in combination with \IPS\Log::log() to inspect a single row of data.

Thanks so much for the info about your experience. I'd love to move to IPS Cloud, but I want a simple way to know the cost. Right now I'd be guessing.
Does IPS show the number of page impressions in the AdminCP? If I knew this, I'd be able to look at the cloud plans and know which one fits my needs. 

I was not aware of this advertising twist but for you guys that self-host I will tell you from first hand experience that the IPS cloud service is excellent and they need to get the word out somehow about this service. I self hosted a IPS site from 4-2011 thru 4-2018 and I can't tell you how many years that dealing with different hosting companies took out of my. From completely corrupt up charging hosting companies to the totally inept hosting services. Plus, the learning curve associated with self-hosting is a total pain in the ass.
I am primarily a content guy, know how to run a community guy and a guy that doesn't want to deal with hosting. I have been with the IPS cloud service since 4-2018 and I hope to never go back to any type of self-hosting scenario. In the past 4 yrs we have not had a single hosting issue since we have gone with the IPS cloud package. I have been a huge advocate for IPS to create a turnkey one stop shop so I would not have to go thru the intellectual hurdles of self-hosting. 
Now that IPS has gotten closer to the expanded media storage levels I see no reason to ever switch. No shill here but I will tell you from first hand experience, I love the IPS cloud package. I hope my testimonial will compel some of you to at least explore switching from self hosting and if you do end up making the move, it will result in you having more time to spend on your community admin needs. Additionally, you will be able to take some of the time you will save from dealing with hosting issues to having extra time to enjoy life.

There's already a merge topic function under Moderation Actions, assuming I'm understanding you correctly. If you literally mean only the first post in a topic, what are you trying to accomplish and what would happen to the rest of the posts in the source topic?
 

I'm sorry for the delay and your frustration. Your transaction was caught by our fraud screening filters with an unusually high risk score. This transaction should have been automatically declined, which would have provided immediate feedback. I apologize for the lack of communication. 
As noted in your ticket, we have manually approved your second transaction. We appreciate the opportunity. 

I'm sorry for the delay and your frustration. Your transaction was caught by our fraud screening filters with an unusually high risk score. This transaction should have been automatically declined, which would have provided immediate feedback. I apologize for the lack of communication. 
As noted in your ticket, we have manually approved your second transaction. We appreciate the opportunity. 

I'm sorry for the delay and your frustration. Your transaction was caught by our fraud screening filters with an unusually high risk score. This transaction should have been automatically declined, which would have provided immediate feedback. I apologize for the lack of communication. 
As noted in your ticket, we have manually approved your second transaction. We appreciate the opportunity. 

This ONLY impacts legacy "Standard 25" and "Plus 40" customers at this time. If you did not receive an email, it is because you are not on those packages and no further action is necessary.

This ONLY impacts legacy "Standard 25" and "Plus 40" customers at this time. If you did not receive an email, it is because you are not on those packages and no further action is necessary.

On January 22, 2022, cloud service will be temporarily suspended until such time that a new package is selected. We felt this was a better (albeit less than ideal) alternative to automatically upgrading packages. There will be a 60 day grace period to reactivate an account on a new package, or receive a full backup of the account. After the 60 day window, the account would be purged, per data retention policies
I hope that answers your questions and helps alleviates some potential fear and uncertainty. 

This ONLY impacts legacy "Standard 25" and "Plus 40" customers at this time. If you did not receive an email, it is because you are not on those packages and no further action is necessary.

This ONLY impacts legacy "Standard 25" and "Plus 40" customers at this time. If you did not receive an email, it is because you are not on those packages and no further action is necessary.

On January 22, 2022, cloud service will be temporarily suspended until such time that a new package is selected. We felt this was a better (albeit less than ideal) alternative to automatically upgrading packages. There will be a 60 day grace period to reactivate an account on a new package, or receive a full backup of the account. After the 60 day window, the account would be purged, per data retention policies
I hope that answers your questions and helps alleviates some potential fear and uncertainty. 

On January 22, 2022, cloud service will be temporarily suspended until such time that a new package is selected. We felt this was a better (albeit less than ideal) alternative to automatically upgrading packages. There will be a 60 day grace period to reactivate an account on a new package, or receive a full backup of the account. After the 60 day window, the account would be purged, per data retention policies
I hope that answers your questions and helps alleviates some potential fear and uncertainty. 

Yes; by upgrading. 🙂
Seriously though, there is no other way to dismiss it permanently, I'm sorry.

Yes; by upgrading. 🙂
Seriously though, there is no other way to dismiss it permanently, I'm sorry.

@Matt @Lindy @Charles @Jordan Miller
I would like to acknowledge and thank you for the compromise re 6-month renewal. It's fair to say that I was vocal and extremely critical (and negative) in my reactions to this situation. I'm glad there has been an acknowledgement of the failings and a compromise to ease the impact on smaller communities like mine.
While the price increase still respresents a challenge for my site, being on the smaller hobbyist side of the spectrum, the reintroduction of the 6-monthly renewals does at least give us some breathing room to try to accommodate the new prices by reducing the short-term burden on us.
I'd like to add my tuppence worth now that things have calmed down.
I'd ask, as others have done, that any changes to pricing or service offerings be communicated in a timely fashion in the future to give us time to deal with said changes.
I would also suggest that a consultation process with a core user group would be beneficial, for any proposed changes to services. If this was broadly representative of your customer base, and used to test and vet ideas in advance of implementation, issues such as the ones debated in this thread could be identified and solved in advance. We're here and we're vocal, and I personally would be only too happy to form a part of that. I've been an advocate of your team and services for so long, and it was truly upsetting to suddenly find that trust shattered. I believe the community being more engaged would have alleviated much of this situation.
Finally, I don't expect IPS to hold its prices, even for a short period, which I've said numerous times in this thread. I'd absolutely support smaller incremental price increases inline with inflation to help maintain development of the product and services. These smaller increases would be far easier to plan for and to absorb.
P.S. I apologise for any typos, the spellchecker in Firefox does not seem to recognise this as an editor. 🤔
P.P.S. I am not switching to Chrome. 🤮