Daniel F

Is this 4.6 or 4.5? I remember that I fixed here few bugs for 4.6. Could you please review ALL your groups and ensure that they have valid max.upload file size values. This MAY help, if not you'll have to wait for 4.6

Could you please submit a ticket so that we can take a look a this.

We're using here a custom template which doesn't have the id included, but I've noticed few issues with the current approach. I've posted an internal bug report for this

Is your globalTemplate customised? It's already there: {{if isset( \IPS\Request::i()->id )}}data-pageID='{expression="(int) \IPS\Request::i()->id"}'{{endif}} My demo board output: body class="ipsApp ipsApp_front ipsJS_has ipsClearfix cCmsDatabase_articles" data-controller="core.front.core.app,core.front.widgets.manager" data-message="" data-pageapp="cms" data-pagelocation="front" data-pagemodule="pages" data-pagecontroller="page" data-pageid="7" data-pagename="articles.html"

Welcome to part 3 ( Part 1 & Part 2 ) of our series for 3rd party developers. Let's recap the interesting stuff: A new extension was added to the core app to allow 3rd party apps to extend the achievements. Content Items can be marked as anonymous We have cleaned up our code and have removed almost all the deprecated methods and variables! One if the most concerning changes for IN_DEV users will probably be our new ACP warning once the CSRF Key is being exposed in the ACP That's nothing to worry about, it's only returned with enabled IN_DEV mode, but please take it serious and try to avoid any redirect to any URL containing the CSRF key and containing user generated content.

Could you please submit a ticket so that we can take a look at this?

I love Polaroid photos. ( We had a camera, but I replaced it with a modern approach => replace the camera with a Polaroid printer:D ) Make 10 pics on the iPhone or camera and then send the best to the Polaroid printer🤣 Old School Results where nobody knows if the baby on the pic is me or my daughter... MUCH MORE FUN!!!

Time to upgrade! 😉 From the 4.5 changelog:

There should be a full error stack logged in your system log. Try to find the last error in the twitter_promote category

We’ll mention the IP address in the support request once it gets necessary:)

You can use the filter on the club - members page to show all invited members. That said, as far as I know, they won't get a duplicate invitation if they were already invited.

There's indeed a rule for this in our guidelines https://invisioncommunity.com/developers/submission-guidelines/

That's already possible out of the box with IP.Pages and some custom coding to the templates.

That's caused by a bug which was fixed for 4.6

@Ilya Hoilikhere we go:)

What's the returned error?

Thanks. Based on our code ReadMarkers support Items without containers, so it's a valid bug which I have posted to our internal bugtracker.

{text|raw} won't escape the text. But please be very careful 😉 NEVER do this with usergenerated content

We have an internal suggestion for this already 🙂

What’s wrong with the pages app?

No, it means that the end user will need to cancel any active withdrawal request (per currency) before creating another. So if you create a withdrawal request today, you won’t be able to create a second one until the first was completed or canceled .

You could use our Pages application and just create a new database for job positions 🙂

BTW, if you're hosted with us, you're of course able to create the robots.txt too 🙂 Just mentioning it here for our cloud clients which probably run into this topic.. 🙂

Few months have passed since our last post here, so let's get ready to rumble🙂 Supported PHP & MySQL Versions: The PHP min version was increased to PHP 7.2 in IPS 4.6, this means that your marketplace submissions are required to work with this version, but keep in mind that few clients are going to use php8, so I would really suggest to try to get your code working with both versions, which means that you'll need to implement some changes to avoid some BC breaks in PHP8. Here's a great list https://www.php.net/manual/en/migration80.incompatible.php Security Improvements: I have mentioned this change in another topic today, so let's recap it here too:) We have a new IN_DEV code check similar to the slash check, which will inform you about any outputs containing the CSRF key in the URL. This is a bad practice allowing attackers and 3rd parties to obtain the users CSRF key, so please try avoid this at any cost! We're not going to reject MP submissions because of this, but please try to avoid this as much as much as possible. Withdrawal Requests: Please keep in mind that you're permitted to have only one payout request per week;) Since this didn't work out that great and to avoid any drama about canceled requests, this is going to be handled now automatically. As long as there's an open request, you won't be able to submit any new requests! But don't worry, you'll still be able to cancel it and create a new request!