mr-pimpen

Non-Amazon S3 storage services do work with IPS 4.1x. Add your endpoint, key, secret, and sub-directory and custom url if needed, assign to some file category such as attachments or Gallery images and off you go! However, these Non-Amazon S3 services are NOT officially supported by IPS - that's because some of the internal methods have not been altered to handle them. These methods are hard-coded for Amazon S3 exclusively. If you are merely displaying images and the like on the front end, none of this is a problem. It becomes a problem if your end-users are going to download these files - that is when you hit the exclusively Amazon S3 code and the downloads will fail. For example, if you assign non-Amazon S3 storage to save IPS Downloads files, those files will not be downloadable. When the system attempts to make the download URL, it crafts that URL as if you were using Amazon S3, not some other S3-Compatible storage service. The two major areas that this will impact are IPS Downloads files and Attachments (this is what the file storage is called in the Files list in the ACP - it encompasses all attachments such as those you would have anywhere the full editor is used and there is an attachment dropzone.) This plugin intercepts the the URL creation method called on Amazon S3 file storage objects, checks to see if it is an actual Amazon S3 request, and then just passes it on through as usual. If it is NOT an Amazon S3 request, it must be an S3 compatible method, in which case I provide a rudimentary URL to patch this up. It isn't anything fancy: just enough headers to push out the actual file name and trigger your browser to download it. If the attachment or file in question is an image your browser might just pop it up in a new tab, in which case just right click and download it there. This has been tested with the usual modern browsers (minus Safari), and various file-types. All testing was successful. BTW, as an aside, external FTP storage for files is NOT COMPATIBLE with IPS Community in the Cloud. Might want to note that... Free, support through the IPS Marketplace topic for now. Free also means lay off the instantaneous demands for support. I use this too so it's in my interest to keep this going. Support, and this plugin's existence, continues until IPS gets around to actually officially supporting Non-Amazon S3 storage. WARNING! The only item in the entire IPS Suite that marks files as private is IPS Downloads. This plugin will flag them as public. This means a few things: 1) If you are monetizing or otherwise require to fully control access to IPS Downloads files this is probably not the plugin for you. You will need to wait for complete 3rd Party S3 support, or at least specific mods to support obj.space, Digital Oceans Spaces, and so on. It really is just some hump work on getting the signatures correct (and it might be a V2 vs. V4 dance with varying providers as well - IPS just has a hard-coded-to-Amazon V4 method). Give it time, it will happen. 2) If you are using this plugin on an already existing bucket with Downloads files, those files will need to be flagged as public-read for them to download correctly. Again, this plugin is just getting rid of the signatures to allow public files to download correctly from 3rd-party S3 providers. 3) IPS Downloads users on IPS Community in the Cloud may need to wait forever and ever before the plugin will work correctly (forever and ever being defined as more than handful of minutes) as CIC caching takes some time to get things working. You *will* need to be infinitely patient. Like, install and then go drink something for awhile, read a book, etc. Then test. Don't yell at me saying this is broken., It isn't. Tested and verified on both own-hosting and CIC. Enjoy, good luck, etc...

About This File Will swap REVIEWS and COMMENTS tab positions in event view.

About This File For one of my projects I needed the possibility to read data from my board. I could not use the built in API because one important thing still is missing: user authentication and only get data the user is allowed to read. So I wrote my own REST API, including user authentication with tokens and a fluent data output. Currently it is not possible to write data. But the plan is to implement that feature in the future. The plugin is currently in a beta state and available for free. In the future there a plans that you have to purchase it. Installation Install the application through uploading it in the ACP Navigate to "Community" > "Itzrest" > "Settings" and insert a random 32 length key. This step is only needed if you want to use authorized access to the API. The key will be used to encode user tokens and authenticate the user if you make API calls. Make sure your webserver supports authentication headers. Otherwise authorized access will not work. That's it. Everything should work like a charme right now. Go on with the next topics Implemented endpoints Currently the following endpoints are implemented (more will be available in the future). And again: at the moment it is only possible to read data. You must prefix every endpoint with /restapi". Forums /forums /forums/<forumId> /forums/<forumId>/topics /forums/posts /forums/posts/<postId> /forums/topics /forums/topics/<topicId> /forums/topics/<topicId>/posts Core /discover/unread /discover /reactions /reactions/<reactionId> /staff/users /staff/users/<userId> /staff/groups /staff/groups/<groupId> /messenger/folders /messenger/folders/<folderId> /messenger/folders/<folderId>/conversations /messenger/conversations /messenger/conversations/<conversationId> /messenger/conversations/<conversationId>/messages /messenger/messages /messenger/messages/<messageId> Calendar /calendars /calendars/<calendarId> /calendars/<calendarId>/comments /calendars/<calendarId>/events /calendars/comments /calendars/comments/<commentId> /calendars/events /calendars/events/<eventId> /calendars/events/<eventId>/reviews /calendars/events/<eventId>/comments /calendars/reviews /calendars/reviews/<reviewId> Gallery /gallery/albums /gallery/albums/<albumId> /gallery/albums/<albumId>/images /gallery/albums/<albumId>/comments /gallery/categories /gallery/categories/<categoryId> /gallery/categories/<categoryId>/images /gallery/categories/<categoryId>/albums /gallery/reviews /gallery/reviews/<reviewId> /gallery/comments /gallery/comments/<commentId> /gallery/images /gallery/images/<imageId> /gallery/images/<imageId>/comments Authentication /auth/login /auth/authenticate Login as user To login as a user you must send a POST Request to the /auth/login endpoint with your username and password: curl \ -d username=max\ -d password=secret\ -X POST <baseurl>/restapi/auth/login As result you will get an object with several user data and the most important thing: the access token: { "data": { "id": "1", "name": "max", "access_token": "********", "photoUrl": "", "birthday": "" } } Keep the token secret and use it for authorized API calls how described in the step "make authorized requests". If you use authentication it would be the best way if you use a secure (https) connection to make API calls. Make requests Nothing more than sending a GET request to a specific endpoint: curl <baseurl>/restapi/<endpoint> For example: If you want to have all available calendars from your board: curl POST <baseurl>/restapi/calendars Your result will be something like that: { "data": [ { "id": "1", "title": "Community Calendar", "title_seo": "community-calendar", "color": "#6E4F99" } ] } Make authorized requests For authorized requests you need an access token. Append the access token as authorization header and make your request: curl \ -H "Authorization: Bearer <token>" \ -X <baseurl>/restapi/forums You can validate if your token is valid by sending a request to the /auth/authenticate endpoint: curl \ -H "Authorization: Bearer <token>" \ -X POST <baseurl>/restapi/auth/authenticate As result you should get a valid user object. Pagination, order If your board has thounsands of posts or threads we must paginate the results. Otherwise the performance of your requests will be horrible. Each endpoint accepts query parameters to sort and paginate your results in an easy way. Therefore each endpoint has a meta node in its result whicht give you information about your current agination state: "meta": { "pagination": { "total": "22", "count": "22", "per_page": "25", "current_page": "1", "total_pages": "1", "links": [] } } Now let us filter / paginate and limit our results: curl <baseurl>/restapi/forums/2/topics?order=title&orderDirection=asc&limit=5&page=2 We will get the following meta output: "meta": { "pagination": { "total": "22", "count": "5", "per_page": "5", "current_page": "2", "total_pages": "5", "links": { "previous": "<baseurl>/restapi/forums/2/topics/?page=1&order=title&orderDirection=asc&limit=5", "next": "<baseurl>/restapi/forums/2/topics/?page=3&order=title&orderDirection=asc&limit=5" } } }