bfarber

The reason a post is held for moderator approval isn't really logged when the post is made, so there's no where we could retrieve it from right now to display.
If you submit a ticket, we might be able to investigate on your site directly and help you identify the reason.

Sounds like it's a webp image that has been renamed to ".jpg". If that is the case, our backend won't be able to process it properly and that would explain the error.

It was a bug and now fixed 🙂

I was going to respond...but forgot what I was going to say.

I'm finding it to be a lot faster locally with IN_DEV enabled actually.
I had to adjust the regex you supplied (it didn't account for typed parameters like function x( $member=NULL, \IPS\Member\Group $group ) ) but it was pretty helpful nevertheless. Thanks! I found a few more similar issues (method_exists() calls on NULL for instance) but nothing you hadn't reported. Let us know if you spot anything else.

There is no built in option to store attachments in Gallery (or Downloads or any other app). That said, it strikes me as illogical you would give a user unlimited space in Gallery but a restricted amount of space in post attachments. An uploaded image is an uploaded image.

Zapier integration is currently in beta stages and CIC clients can sign up.

I didn't see SELECT_SQL_CALC_FOUND_ROWS referenced there still. I believe the documentation was already updated.

If you are getting an error like this, it sounds like a bug. I'd recommend submitting a ticket.

1. Pagination is typically generated within the PHP controller, and then the appropriate template is included within theme templates.
\IPS\Theme::i()->getTemplate( 'global', 'core', 'global' )->pagination( $this->baseUrl, $this->pages, $this->page, $this->limit, TRUE, $this->paginationKey, $this->simplePagination ) Swap out the parameters as appropriate of course. Alternatively, you can use something like the table helper (\IPS\Helpers\Table) which handles things like pagination automatically.
2. You should not need to pass any content in the database through any sort of parser before putting it in the editor.

Ah, usually these things are triggered by a controller on it and I didn't have the files open to verify at the time I replied. Sorry for the confusion.

Fair enough, I've raised it internally.

You probably have to define the "Drug" array entry first.

Add a file constants.php starting with "<?php" (if it doesn't already exist) and then add this new line to it:
 
define( 'RECOVERY_MODE', true ); Get into the ACP, disable whatever you need to disable, and then remove the line from the constants.php afterwards.

There is no built in way to do this, and frankly Facebook, et al don't want you to either. You can link your Facebook and Twitter accounts to use the "Promote" tool within the software, which is a moderator/admin-level feature.

Instead of trying to add an additional parameter input to a template (which would be challenging, but doable), I'd instead just duplicate the template in your plugin and add the additional parameter there.
 
That said, if you're bent on adding an additional parameter to the existing template (keep in mind a future update could cause all sorts of weird things to happen if you do this, so be prepared to maintain this plugin), you can redefine the entire method in a theme hook file. Create a theme hook on the appropriate area, and then redefine the template method in the theme hook file. Semi-example here where I overwrote the calendar view template group for an app:
 
//<?php /* To prevent PHP errors (extending class does not exist) revealing path */ if ( !defined( '\IPS\SUITE_UNIQUE_KEY' ) ) { exit; } class locator_hook_calendar_event_view extends _HOOK_CLASS_ { /* !Hook Data - DO NOT REMOVE */ public static function hookData() { return parent::hookData(); } /* End Hook Data */ public function view( $event, $commentsAndReviews, $attendees, $address=NULL, $reminder=NULL ) { \IPS\Output::i()->cssFiles = array_merge( \IPS\Output::i()->cssFiles, \IPS\Theme::i()->css( 'calendar.css', 'locator', 'front' ) ); \IPS\Output::i()->jsFiles = array_merge( \IPS\Output::i()->jsFiles, \IPS\Output::i()->js( 'front_calendar.js', 'locator', 'front' ) ); return \IPS\Theme::i()->getTemplate( 'calendar', 'locator' )->view( $event, $commentsAndReviews, $attendees, $address, $reminder ); } } As you can see, I overwrote the PHP method generated by the template files...you could use this approach to add the new parameter.

We do post minimum recommendations for MySQL and PHP.
For the "Dynamic" row format, we would recommend moving all tables to this format. But it's not a requirement, and if you aren't having issues you do not necessarily need to make any changes.
The note about future versions supporting certain things is a generic message just to indicate why we make recommendations.

This is really what it comes down to. As the backend evolves, sometimes changes like this become warranted, even if not necessary (which is why this is a recommendation and not a requirement in the checking tools). Just like MyISAM storage engine was the preferred engine for years, but not we strongly recommend InnoDB for just about everyone.

Certain older registrations may not be cleared in some cases, specifically if they've ever visited (or rather, have a last_visit timestamp on the account set). We intentionally do not clear abandoned registrations if the account has ever been flagged as "used".

The Pages application databases support a "publish date" field, so you can easily do this with pages. You just adjust the "publish" date when you publish the article/record.

You use custom.css and target whatever you want on the page. You can start with something like
[data-pageApp="core"][data-pageLocation="front"][data-pageModule="system"][data-pageController="register"] ...  

If a Pages database record is deleted, its record image is deleted. There is no central location to view all record images I'm afraid.

We output structured data in the form of JSON+LD. You can see this by validating any of our "blog" articles (which are actually generated through Pages).
https://search.google.com/structured-data/testing-tool/u/0/?utm_campaign=devsite&utm_medium=jsonld&utm_source=review-snippet#url=https%3A%2F%2Finvisioncommunity.com%2Fnews%2Fcommunity-management%2Fwhat-is-the-engagement-trap-and-what-to-do-about-it-r1168%2F
If you wish to remove the "article" markup and insert your own, you will likely need a plugin written. If you have some universal ideas related to structured data markup you think would be valuable to the community at large to support out of the box, please feel free to share them.

Have you tried making it a div instead of a span? Also, it may be wiser to set these values in css and place a class instead, so that you can adjust this in the future more easily, rather than hardcoded style elements within the stored body.
Something like:
<div class="myRightFloatingImageClass">{content}</div>  

You can't disable default skin. Mark other skin as default and delete it.