Mote Marketing, Inc.

You guys, I apologize. You are absolutely right. Please disregard everything after I opened my yawning cakehole.

Stuart, although I certainly appreciate the response, talk about stating the obvious! ALL payment gateways are "third-party" developers! IPS does not own any payment gateways. However, several IPS help articles (such as this one) unequivocally state that the Square payment gateway was added to the list of IPS-supported gateways. This IPS article unequivocally gives (characteristically incomplete, vague and therefore useless) "instructions" for integrating Square as a payment method. As you can plainly see, it says to install the payment gateway, but (as usual) gives no guidance on how to do that! We have already created the Square application, and now simply need to install it in the IPS ACP. So, with all respect, what are you talking about? I'm not making this up out of thin air...I'm relying on IPS-created tech articles, for Pete's sake.

Various community articles (such as this one) seem to suggest that the Square Pay platform is supported by the IPS Commerce app, and say that you add new payment method, and select "Square Up Payment Gateway", but that option does not appear in my "Payment Methods" screen. Is this just another example of the IPS Help articles being woefully out of date, or...what? Can someone please point me to the correct instructions for integrating Square Pay?

You guys were spot-on correct! It was the PHP path. Hey, THANK YOU. Much-obliged! Charles

Daniel, I am showing that we are on PHP v8. Can you tell me where and what I need to update exactly? I'm logged into my server via an SSH session, and have opened the only CRONTAB, which shows exactly what the IPS ACP message calls for. Apologies if this is obvious. Is this updated via the php.ini file? I don't see anything in the CRONTAB file that seems to fit. The CRONTAB text is as follows, which is exactly as called-for in the IPS ACP error message: /usr/bin/php -d memory_limit=-1 -d max_execution_time=0 /homepages/31/d850801269/htdocs/applications/core/interface/task/task.php bd4b1a5e006ebb39f2f04ba352590a4d

Thanks Daniel. I don't believe we've updated our PHP version, but let me check.

As required by the IPS app, I have a CRON job that's been setup and running successfully every minute for nearly a year. But today, when I logged-in, I was greeted with the dreaded red "maintenance tasks not running" error. I have confirmed that the CRON job is still running. What am I supposed to do now??

We have two persistent Admin notifications that we cannot clear (see attached image), despite the fact that all of these functions are absolutely disabled in our php.ini file. My Developer says that this is a commonly-known issue with the IPS platform, but while it's certainly not the "end of the world", it is annoying to have false errors displayed, and tends to diminish the perceived importance of any real errors that might crop up. Is there any way to clear these?

Any thoughts on this?

I assume you mean to click the "gear" icon. That worked. Thank you!

Hi Jim, Thanks for the reply. No, push notification are not enabled. If I click "Enable" (either in the auto-generated popup or /notifications/options/), it says "Enabling..." permanently (hence my previous "endless loop" comment). Here's the Browser Console error output when I click "Enable": sendRemoveListener on closed conduit firefox-addon@expressvpn.com.2886218023767 ConduitsChild.jsm:112 _send resource://gre/modules/ConduitsChild.jsm:112 _send self-hosted:1282 removeListener resource://gre/modules/ExtensionChild.jsm:670 removeListener resource://gre/modules/ExtensionChild.jsm:905 onChanged chrome://extensions/content/child/ext-storage.js:332 removeListener resource://gre/modules/ExtensionCommon.jsm:2511 revoke resource://gre/modules/ExtensionCommon.jsm:2533 close resource://gre/modules/ExtensionCommon.jsm:2538 unload resource://gre/modules/ExtensionCommon.jsm:899 close resource://gre/modules/ExtensionContent.jsm:935 destroyed resource://gre/modules/ExtensionContent.jsm:1011 observe resource://gre/modules/ExtensionContent.jsm:1029 Again, this problem only affects Firefox.

Please modify the search box in this screen to search and return user-entered "Translation" values (as opposed to only the original IPS keys/text). We have extensive custom translation phrases entered, but unless we keep a separate log of which IPS-native key values were changed, they are forever lost in the ether, unless you want to manually slog through vast numbers of pages hoping to accidentally stumble upon the one you're looking for. Since those user-entered values are obviously stored in the DB, they should be searchable, right?

PS - It's not "cluttered" at all, as it's simply an underline (or other unobtrusive indicator, such as small "Help" info (e.g., "i for info" icons) on or adjacent to existing UI labeling denoting help popups available. That's the entire point (to not clutter the interface with always-displayed help text, but displaying it only when the user wants to see it, which is facilitated by a brief delay in displaying the mousover popup, to avoid inadvertent display unless the user hovers over the desired label for a certain amount of time). The other point is that it intrinsically ties help "articles" directly to the relevant UI elements). Our users have responded quite favorably to this strategy, and the IPS ACP could really benefit from this, since so many features are not at all "intuitive", in terms of how they are intended to work, or what the correct setup options are for any given scenario. Microsoft and others use this approach extensively, so it's hardly controversial or "ground-breaking". It obviously requires a sound balance between brevity (of a popup) and the verbosity of a full-on external Help article.

I was trying to be somewhat charitable, Jonas. 🙂

My Developers confirm that this is an IPS bug (probably specific to the latest update (v4.6.10): Browser: Firefox v97.0 (64-bit). Does not appear to affect the latest versions of Microsoft Edge or Google Chrome browsers. OS: Windows 11 Home, v10.0.22000 (64-bit) Description: The push notifications popup thrown by IPS enters an endless loop when the user attempts to enable push notifications in Firefox ("Enabling..." just keeps churning forever (see attached image).