Jump to content

rllmukforum

Clients
  • Posts

    159
  • Joined

  • Last visited

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by rllmukforum

  1. Earlier today, I updated our server from PHP7.x to 8.0. I then upgraded the forum itself from 4.6 to 4.7. Unfortunately I neglected to disable 3rd party hooks before doing so, although the Invision installer did not indicate there was an update for either. The forum update went just fine, requiring me to perform some manual SQL etc. At the end, I got this message: When not logged in, the site www.rllmukforum.com renders just fine. Once I login, I get a white screen. php-fpm is throwing this error: [28-Oct-2022 16:35:04] WARNING: [pool www] child 13518 said into stderr: "NOTICE: PHP message: PHP Fatal error: Declaration of IPS\forums\ignoretopics_hook_$ [28-Oct-2022 16:35:04] WARNING: [pool www] child 13518 said into stderr: "MovedLinks = false, $location = null) in /usr/share/nginx/html/init.php(..." which presumably confirms it's due to the Ignore Topics hook. Without access to the admin panel in order to disable this hook (assuming the board did not), how can I bring my site back online? I would file a support ticket but I've just realized we no longer have email support (something to fix later) and I cannot submit a ticket through the ACP as I used to. Appreciate any help! We're essentially offline until I can get this resolved.
  2. No, we aren't on the latest release, that's on the to-do list. Great, looks like things will be sorted very shortly then!
  3. This seems to work for subscriptions and other things in the store, but not for donations. Any ideas? This is exactly what happened to us, but with a lower volume before Stripe stepped in and suspended our account. We have had about £450 in donations over the last few years so I am loathe to turn that off, so it would be ideal if donations could be restricted to members in line with everything else.
  4. Thanks for the help Randy. I'm trying to work out how to set it so that guests can't check out - is it a case of creating a fraud rule which refuses if the person is in the "guests" group?
  5. We have just had a notification from Stripe that our account is being used for card testing - and indeed, we are getting a huge number of small donations into our Stripe account, the majority of which are failing. I have now turned on the setting requiring people who are paying to set up an account, which should reduce this issue somewhat, but Stripe also recommend that we add other mitigations to our payment gateway, including some added friction. Their help page is at https://stripe.com/docs/disputes/prevention/card-testing I can't see that we would be the only people to have suffered from this. Does anyone have any advice - and can IPS add some parameters to the payment gateway to help overcome this?
  6. I had run it a couple of times before making the post, to no avail. However, I noticed it's now working. I'm not 100% sure what I did to cause that. Possibly disabling the apps noted above and re-enabling. I also tried dragging Ignore Topics above Ban Members from Forum in the list of applications (I'm unsure what, if anything, this order signifies). Appreciate the video, I wasn't sure where application settings were to be found in the ACP.
  7. We just bought this app and installed on 4.6.8 but are having trouble getting it setup and working. We see the "Ignored Threads" section on Account Settings, but that's the only indication to the user that the app is installed. I have it enabled, and the toggle set to on in the application's permission, and have disabled all other 3rd party apps/plugins except this one. However, we still don't see the Ignore Topic button, nor can I find in the ACP where to define the app's settings. I tried creating a new theme, although our themes are essentially stock except for colors and a logo. For reference, the other 3rd party apps/plugins we have installed are: App: Ban Members From Forums (written by yourself) Plugin: Change Post Author Plugin: Mandatory Report Message Any insight you have to get this working appreciated.
  8. While in Table view and browsing the list of Topics, the topic starter has their name listed on the left and the last user to reply has both their name and avatar on the right. However, in Fluid view the information shown is slightly different. The topic start has their avatar and name on the left, and the last person to reply only their name on the right. This is on a desktop. Here is an example. Table view: Fluid view: When viewing on mobile devices, there are similar inconsistencies. We would prefer the views are consistent and thus align the newer Fluid view to how Table view has traditionally displayed this information. Ours is quite an old community and have only recently discovered Fluid. It's generated quite a lot of interest and we're hoping to provide some constructive feedback on how it might be improved.
  9. Our forum is quite old and it only recently occurred to us to start using the Fluid view. Users are really liking it, however the mobile approach of having a drop down selection of forums to include seems to be preferred. Are there any plans to allow the forum selections while on desktop to be collapsed or otherwise hidden?
  10. Users of our forum have started reporting that YouTube and similar videos are now auto playing in iOS. This appears to have started just before the iOS 15 release (e.g, 14.8), although affects 15 too. All embedded YouTube videos on in a topic a user is browsing will start to play at the same time. I haven't been able to find similar feedback given here, although one user did note that it seems to affect other sites, too. It also occurs irrespective of browser. Does not seem to affect Android, Windows, or MacOS. Any help appreciated.
  11. Apologies for the novice question, I'm slowly coming up to speed on using the developer tools to customize our site. We find we get a lot of reported posts without a supplied reason, so want to make that field required. I've created a theme hook and believe I have found here the report dialog is initiated <li class="ipsMenu_item"> <a href="" data-ipsdialog="" data-ipsdialog-remotesubmit="" data-ipsdialog-size="medium" data-ipsdialog-flashmessage="" data-ipsdialog-title="{lang="report_post"}" data-action="reportComment" title=""> {lang="report"} </a> </li> under \IPS\Theme\class_forums_front_topics However, it's not terribly obvious how I go about making the message required before "Submit Report" will function. I've spent quite a bit of time reading the dev docs and searching this whole community for "required field" and other terms, to no avail. I assume we'll also need to edit the language file for report_message_placeholder, as "Optionally enter a message with your report." obviously no longer makes sense. Any help appreciated.
  12. Our forum has been running Invision since 2003, and users are very much stuck in the classical folder paradigm. Attempts to switch or supplement this with a metadata approach (ie, tags) gained little traction. It's not alike an illness, it's being used to a certain way of doing things. And on a personal level, I'm quite happy for forums in general to eschew the need to mimic social media and operate as they did. To each his own, right? Thanks for the marketplace suggestion, I'll look in to that, @day_
  13. Apologies if already suggested, I searched and could not find it specifically. Request: Change all topic title links such that they include the getNewComment parameter. This is the default behavior while browsing from the main site index, but not while in a forum/sub forum. Justification: When the Forum app had separate desktop and mobile themes, the mobile theme had this very functionality. Rather than requiring users to click the little dot/star alongside a thread, you could click the thread title to see the first unread reply. I no longer run analytics, but even as of a few years ago, half of my users are on mobile devices. We manually edit themes to include getNewComment, but I would prefer to perform as little customization as possible. If, for some reason, a user wants to return to the first page, the forum already includes a link to page 1 under the topic title. I believe this would, technically, allow you to remove the dot/star, which cleans up the UI slightly. It feels like a good quality of life improvement for mobile use, much like the recent new features added in 4.3.
  14. Thank you, I appreciate the technical analysis. I will trust that the above means some plugins require a specific version for IPS 4.2. I think the issue is language; something "compatible" with 4.2 literally doesn't preclude compatibility with prior versions. Also, as I have stated, other plugins we have used, for older versions of IPS, have not require separate versions. If the plugin had stated "4.2 required", I would have initially downloaded the previous version, 1.1.6. Thanks for taking the time to explain why the change was necessary, it's not always clear why Invision mess with templates in this manner.
  15. No sir, I do not. I am literally offering only my experience of having installed other IPS plugins. By pure chance, these other plugins have needed tweaks to adapt to changes Invision made to their code. In these specific instances, the plugins then worked with the current and prior versions of IPS. I have no knowledge of this plugin nor any of the underlying programming knowledge in IPS framework. I'm simply a paying customer who is 1) having difficulty and 2) seeking help by asking questions. I am disappointed in the outcome of our interaction. Thank you for your time.
  16. I've seen numerous plugins that need to be tweaked for new versions of IPS, due to changes Invision have made, but retain compatibility with older versions Not trying to be difficult, this is just my experience of plugins and so I did not understand the requirement for this one.
  17. Yeah, running the support tool fixed the post issue. I'll try reinstalling the plugin later to see if it reoccurs. To me, "compatibility" means "also works with", not "is required". Even just a minor heads up in the notes to use the previous version while not on the 4.2 beta would probably save a post from people like me.
  18. Well, this is interesting. Approximately 25 minutes after installing 1.1.6, some members of our forum, myself included, cannot post. I have no way of asking who can and cannot. I've since removed the plugin, but when I try to reply the CKeditor fails to load (I click in the reply window by the placeholder text remains). Also, and curiously, the theme selector dropdown no longer works. Again, anything obvious I might try? I've restarted nginx and php-fpm on the off chance it was that, but honestly, the forum has been running absolutely smoothly for months. edit - running the support tool in the ACP resolved it, although I have yet to reinstall the plugin. Very odd.
  19. That did it. I installed version 1.1.6 and it worked immediately. Could I suggest a change, please? This is the first mod I've seen (admittedly, we haven't used many) where it's not backwards compatible with earlier versions of IPS. Given 4.1.19.4 is the current stable production version, and 4.2 not yet released, I would update the product page for this plugin to make it explicit that the latest version (1.2) only works on 4.2, not that it's "compatible" with 4.2. FYI, our only other plugin is Tapatalk. Thanks again for your help.
  20. Purchased and installed on 4.1.19.4, however the "change author" link does not appear at the bottom of a post. I have enabled the plugin, enabled various groups (including the one I am in) and even toggled the "increment post count", not that I thought it would have any bearing on it. Any sense of where I should begin troubleshooting, please?
  21. I've noticed the same thing with twitter, although I'm unsure of the exact steps to replicate it failing. However, sometimes it fails entirely, others it crops a portion of the embedded content. This has been our experience of 4.1.x since upgrading from 3.4 in April if you're using Firefox, however it now seems to affect any browser.
×
×
  • Create New...