Announcements
7 topics in this forum
-
- 1 follower
- 0 replies
- 474 views
Hi, I wanted to clarify the process for any critical updates you may need to make that may potentially need a higher priority when it comes to a review. A critical issue would be something that causes a large impacting issue to your resource, such as a fatal error that prevents it from working. Submit the new version of your resource with only the fix for the issue, no other bug fixes or enhancements. Specify in the change log what the fix is for (so it's obvious to us what you are fixing). Submit a support ticket asking for an expedited review. Asking for an expedited review doesn't guarantee we'll be able to do it, but we'll try our best whe…
Last reply by Stuart Silvester, -
- 0 replies
- 550 views
Deprecation of the interface directory In order to ensure Invision Community is compatible with modern cloud infrastructures we are deprecating the use of the interface directory in favour of a proper front loader system. We're working on a new solution which will allow HTTP requests to the interface directory. This means, any JS, HTML, GIF files uploaded there will work, even PHP will work, BUT you'll have no access to the IPS framework there. Last months common submission issues: All in all the quality increased, but there are still 2 common issues which are worth to be mentioned. Versions (again) 😉 Please try to pay more attentio…
Last reply by Daniel F, -
- 0 replies
- 462 views
Folks, please try to pay more attention to the version numbers you're using for your customisations! There's just another upset client who can't upgrade his file via the ACP - Marketplace because the system doesn't recognise the new upgrade release as "upgrade" because the recent version has long version 2800 while the old long version is 24344. I hope everybody here sees the issue?! The newer version is lower than the last version. Another common concern confusing clients and our backend is that some developers started going back with version numbers for their 4.5 releases. So from 1.4.2 ( 104020 ) they went back to 1.0.0 ( 100000 ) Personally, I would sug…
Last reply by Daniel F, -
- 1 follower
- 0 replies
- 445 views
Hi and welcome to our new series of updates for our contributors. We'll highlight the most common mistakes, ways to resolve them and also generic improvement suggestions once a month here:) As first, I want to apologies that some files took really long to get approved, but we really expected that new submissions and upgrades would have a better quality, but unfortunately >60% of the submissions ( 90% in the first week) were still not following the new marketplace guidelines, which resulted in a devils circle. Let's recap the last months issues resulting in rejections🙂 Core Database changes. Version details not changed. Us…
Last reply by Daniel F, -
- 3 followers
- 13 replies
- 906 views
We have removed the session id from the ACP urls, meaning that you have to make sure to use CSRF protections in all your methods which change a state! We also advice to use \IPS\Request::i()->confirmedDelete() in all your methods where you're deleting data! One of the few examples from the MP reviews is this code: protected function approve() { if ( !\IPS\Request::i()->id ) { \IPS\Output::i()->error( 'node_error', '2myApp', 404, '' ); } $a = \IPS\myApp\Item::load( \IPS\Request::i()->id ); $a->open = 1; $a->save(); /* Log History */ \IPS\myApp\History…
Last reply by Mark, -
- 4 followers
- 10 replies
- 891 views
4.5 introduces some changes to CSS, so I wanted to provide an overview of those and how they might affect you. IE11 Firstly, we've completely dropped support for IE11. This means you'll start to see newer CSS methods being used that IE11 does not support. Atomic classnames One thing you'll notice as you read on is we're moving towards using atomic classnames for utility styles. What does that mean? Basically, each classname is just a convenience helper for applying one particular style. You build how an element looks and behaves by applying multiple classnames. While this is slightly more verbose in the HTML, it's also much clearer…
Last reply by doc, -
- 1 follower
- 6 replies
- 480 views
Please don't forget that marketplace submissions should be completely installable and uninstallable via the ACP, which means that they shouldn't include any additional files which need to be uploaded to the clients webspace manually. Applications can ship the custom js,image,font etc.. files within the interface folder and themes can utilize the theme resource system to add custom files ( JS, Font, Video, etc..).
Last reply by MIXOH,
-
Recently Browsing 0 members
No registered users viewing this page.