Mike Gholson

Possibly, thanks

Thanks guys, yes I get that you provide a shortcut. But I'm not talking about the shortcut and more about the back end support system that was included. Before I upgraded, you had a warning message on the 4.7 admin panel about the feature going away. In that message there were a few recommended options. I cannot find that message so I'm looking for it. About the email link, I turned it on for a month and now have thousands of spam emails. It's just not feasible without some kind of back-end form or something to prevent the abuse. The old system still allowed some spam through, but it was very good at reducing the crappy bot emails. Maybe it was the form, recaptcha, or ?? Thanks

Guys, nobody answered my question. What are the recommended 'contact us' options? There was a post somewhere about alternatives but I can't find it. I get that technically "contact us" is not removed but the guts of it have been removed. Only thing available now is a method to configure an email address or link to another system. I have people telling me they are not able to get help and I need to fix this crucial part of interacting with my customers. Please help. Thank you. Mike

That's definitely an interesting way to do it. Maybe we could also use the internal database feature of the software? I've been looking at 3rd party options but most of them have a monthly or annual cost, which is typical. However, I am not seeing any kind of method to pass along user information between Invision and the 3rd party application. So basically if someone adds a support ticket, it's up to me to look up their account details and/or ask them to fill out a form with the details. I am sad the included support / contact system was deprecated because I used it a LOT. Mike

Hi all, I read that VBP5 will remove the built-in contact us / support ticketing system. My members use this a lot and I've had some pretty good success making business deals with it. What is the recommended replacement? Thank you, Mike

Upgrade on a basic vanilla install went fine. Hopefully the V4 to V5 upgrades work well... anyone testing upgrades again?

Hi all, Looks like we have to create multiple subscription plans to cover month-to-month vs annual. This causes our subscription page to show too many options. I noticed that 4-subscriptions are showing per page on the new version compared to 3 subscriptions on the old software (good change). However, it would be a LOT cleaner if we gave the customer the capability to use a toggle between monthly or annual billing within a single subscription package. Not to mention giving a discount for annual billing. Something to consider, this seems to be a common theme among subscription plans across the internet. Mike

Thanks Gary. Yeah, I knew about the risk to my main website which is why I created a duplicate. Problem is creating the duplicate also brings over all data including the transactional connections / API keys. When I deleted the payment method on my duplicate/beta site, it sent a command to Paypal killing all subscriptions. There is no disable function (that I could find). I thought maybe Paypal would help me out because the command came from a different URL, however, it was actually a command sent through the API key. They weren't able to re-initiate the recurring subscriptions. They told me the customer needs to re-initiate it. Good thing is the IPB software wasn't affected and it will ask the member to renew their subscription on their renewal date. I'll find a way to get through it. I've already created an emergency fundraiser post so we'll see how it goes. I'm only posting here because I think this is serious enough that others can learn from my bad luck. I was contacted by IPB immediately and happy to see the developers / managers jumped in to help. Mike

Yeah, I *HIGHLY* advise against making any decisions to run a copy of your live site like I did. There's no easy method to control the Paypal gateway. This mistake is costing me monthly revenue to the tune of ~$600/month in lost revenue (~$7,200/yr). Probably enough to kill my community. I am working with Paypal to see if I can get mass-command reversed but they are not easy to deal with AT ALL.

Apparently deleting a payment gateway sends a message to Paypal telling them to shut off every single recurring subscription. I also recommend some kind of confirmation dialog or an opt-out of this process. Mike

Yeah, looks like by attempting to delete my payment gateways from my beta site, I canceled them on my production site. Whatever you do, don't delete the gateways from a beta site if you are running a direct duplicate of your production site. RIP

TBH, it would be nice to add a enable/disable function to the payment methods. This way we can shut off the gateway in times like this. I noticed the system tried reaching out to Paypal to cancel all the subscriptions but it failed (probably due to the domain name). So hopefully my production site wasn't affected by a bunch of cancelations.

Thank you, I disabled email using the constants.php. However, I get an error when I try to remove payment types. See below. TypeError: IPS\File::get(): Argument #2 ($url) must be of type IPS\Http\Url|string, null given, called in /var/www/vhosts/classiczcars.com/beta.classiczcars.com/applications/nexus/sources/Gateway/Gateway.php on line 441 (0) #0 /var/www/vhosts/classiczcars.com/beta.classiczcars.com/applications/nexus/sources/Gateway/Gateway.php(441): IPS\File::get() #1 /var/www/vhosts/classiczcars.com/beta.classiczcars.com/system/Node/Controller.php(1372): IPS\nexus\Gateway->delete() #2 /var/www/vhosts/classiczcars.com/beta.classiczcars.com/applications/nexus/modules/admin/payments/gateways.php(211): IPS\Node\Controller->delete() #3 /var/www/vhosts/classiczcars.com/beta.classiczcars.com/system/Dispatcher/Controller.php(128): IPS\nexus\modules\admin\payments\gateways->delete() #4 /var/www/vhosts/classiczcars.com/beta.classiczcars.com/system/Node/Controller.php(117): IPS\Dispatcher\Controller->execute() #5 /var/www/vhosts/classiczcars.com/beta.classiczcars.com/applications/nexus/modules/admin/payments/gateways.php(61): IPS\Node\Controller->execute() #6 /var/www/vhosts/classiczcars.com/beta.classiczcars.com/applications/nexus/modules/admin/payments/paymentsettings.php(86): IPS\nexus\modules\admin\payments\gateways->execute() #7 /var/www/vhosts/classiczcars.com/beta.classiczcars.com/system/Dispatcher/Controller.php(128): IPS\nexus\modules\admin\payments\paymentsettings->__call() #8 /var/www/vhosts/classiczcars.com/beta.classiczcars.com/system/Dispatcher/Dispatcher.php(169): IPS\Dispatcher\Controller->execute() #9 /var/www/vhosts/classiczcars.com/beta.classiczcars.com/admin/index.php(15): IPS\Dispatcher->run() #10 {main} Is there another method I can use to disable these automatic payments? I'm afraid the system will charge people twice for their subscription (production site and beta site). Thank you! Mike

Hi @Gary, Were you able to get your images to load? I'm seeing the same issue on my test site. I saw that you may have gone to a private message with CCP developer so I can't see if there was any progress on that. Thank you guys! Mike

Hi guys, After making a duplicate of my production site, I was able to get it upgraded with IPB 5 beta1. However, I noticed that emails are being sent to members (from the beta site). Is there a way I can totally disable emails on the beta site? It turns out that all forums and PM's are reset to a "new" status so the emails are flooding. Also, does running a copy of my production site also charge users for subscriptions? I want to know if I will need to disable something else to prevent this. Thank you!

Here are the files that I eventually had to rename to get my upgraded site to finally render properly: Promotions.php NetworkStatus.php Referrals.php I also deleted Promotions row in the menu database (as instructed above). Mike

Hi Gary, Yeah, I went through the fixes in this thread. I deleted the Promotions row in the database and renamed the files. When I rename a file it seems to just move to another file in the FrontNavigation folder. I'm a bit worried about doing this to every single file. But, perhaps that's what needs to be done? I think this is likely something that should be looked at during the development effort. There are a lot of us that have older databases and the upgrade script should account for these conditions. Hoping this feedback can help the developers.

I'm having similar troubles with an Error 500 after installing the Beta1 update (on my test site). You can see it here. Looks to be FrontNavigation. I have a database from waaay back possibly 2013. Mike

I'm ready!

Is there an ETA or published release schedule for IPB5 ? I am very interested in this upcoming release.

Yeah, IPB5 will be pretty sweet, from what I can tell. Looking forward to seeing more from the team. I find it extremely satisfying to see how active the developers are making a difference in our communities. Also heavy involvement with us is key and you are hitting that nail on the head too. Much appreciate everything you guys are doing!!