Jump to content
Announcing Achievements! ×

Community

imJexs

+Clients
  • Posts

    73
  • Joined

  • Last visited

About imJexs

  • Birthday 04/11/1995

Profile Information

  • Gender
    Male
  • Location
    Austin, Texas, USA

Recent Profile Visitors

6,365 profile views

imJexs's Achievements See all achievements

Enthusiast

Enthusiast (5/13)

  • Reacting Well Rare
  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter

Recent Badges

12

Reputation

  1. Awesome! I can't wait for full release. 🙂 Cheers.
  2. Does the new `downloads/files/{id}/download` endpoint work with S3 storage? Currently any files uploaded to Downloads that are stored in S3 need an access token created before it can be downloaded by a user. The existing endpoint `GET downloads/files/{id}` does not provide a proper URL to download from as S3 gives "AccessDenied". Will the new endpoint provide a proper URL to actually be able to download the file from?
  3. One of the biggest things that has turned me away from the IPS Calendar over the years is the lack of support for iCal RRULE BYDAY. Our community has many events that occur on the first Wednesday of the month, third Saturday of the month, or fifth Thursday of the month (this is a rare occurrence but it happens). Adding support for these edge cases would be amazing and it would also make IPS Calendar more compatible with importing Calendars from other providers like Google Calendar as well as exporting to Google Calendar which would be extremely useful for our members. I did notice that the following comments: //@todo [Future] We do not support HOURLY, MINUTELY or SECONDLY "FREQ" values //@todo [Future] We do not support the properties BYSETPOS, BYYEARDAY, BYMONTH, BYHOUR, BYMINUTE, BYSECOND, BYWEEKNO, WKST //@todo [Future] We do not support complex BYDAY values, such as 1TU or -1FR //@todo [Future] We do not support multiple values for BYMONTHDAY, nor do we support negative values were included in: \IPS\Calendar\Icalendar\ICSParser::parseRrule() which is very exciting, I'm just hoping we could get this added sooner rather than later. Best Regards, Jexs
  4. I am working on an application that will be storing a large number of IP addresses from a variety of sources, but I'd like to be able to systematically update the IP's with their current country code. First instinct is to use the \IPS\GeoLocation class, however, I will be making many calls to this API a day and I just want to check the rate limit before I do this. I would prefer to be able to use this, but I could understand if you don't want this receiving an abundance of calls and I can look into an alternative. Thank you.
  5. Hey @ehren. , I just wanted to check if you have any sort of ETA for the 4.3 updates and if you're already working on them. I know 4.3 is still in beta, but I'd love to be able to upgrade ASAP but that won't be possible as the search functionality is broken on the theme. Thank you for any updates. Love your work!
  6. I think you misunderstood me. I know of the SDK and whatnot. I've written a few applications before, just haven't messed with the front end much. But apparently I just need to triple check things before I write them off. I just tested the js include from your original post and it works now. I have no idea what I missed the first time, but it's working. Much appreciated.
  7. So the file I found that makes the magic happen is located in /dev/js/admin/mixins/ips.core.table.js It's not located in the applications/core/dev/js directory. So is the root /dev/ directory considered the core app as well? I guess I'm not sure how the root /dev/ directory works
  8. Hey BomAle, thank you for your reply. I actually tried that to no avail. I may have been doing something wrong, but I don't believe so. It seemed to be only loading the front-end ips.core.table.js file from what I could tell in the browser developer tools. However, I suppose I just needed to get some sleep. When I woke up I just tried copying the /dev/js/admin/mixins/ips.core.table.js file over to my application in /applications/myapp/dev/js/front/mixins/myapp.mixin.table.js and it works just fine. I'm not sure what I changed that I was trying to last night, but it seems to be fully functioning and I couldn't be happier. With that being said, I would prefer to have my app load the .js file directly from the core to require less maintaining whenever/if ever IPS updates the file with future releases. So if anyone would be able to help load the ips.core.table.js file from the admin panel rather than the front-end, that would be a great help. Also, the code used to import the js file is: \IPS\Output::i()->jsFiles = array_merge( \IPS\Output::i()->jsFiles, \IPS\Output::i()->js( 'mixins/myapp.mixin.table.js', 'myapp' ) ); Thank you for the help. It's greatly appreciated.
  9. So I actually came across something interesting. The thing I tried by including the mixin file works great when working on it in dev mode, but as soon as I took the site out of dev, it stopped working as intended. Any idea what could be causing this? Thanks!
  10. Just tested his method actually. Including the file: /dev/js/admin/mixins/ips.core.table.js Allows the quickSearch to work perfectly fine. Now to tackle the issue of it working on multiple fields...
  11. This is exactly what I'm trying to avoid right now. It seems kind of counter intuitive to implement my own when IPS should support it by default (at least in my opinion). Would you be willing to share yours? I completely understand if no. I was looking through bfarber's post in this: which I'll probably do some more research into before writing any code myself. Best, pndemc
  12. This doesn't seem to be the exact solution for my particular problem, but it is definitely on the right track. I think I'll actually rework my tables themselves to make them a bit more friendly for this type of work. While the link did not answer my question specifically, it does answer the general concept of my question so I'll mark it as the answer for future reads.
  13. Let's say I have 3 tables. They are as follows: users logins names The users table contains an auto incremented primary key as well as a user_unique which is a unique identifier for a user. The names table contains an auto incremented primary key as well as a name_unique which is a unique name to this table. Now assume that a user can login with their user_unique BUT they can choose any name they want. So multiple users will end up with the same name_unique. Inside logins it simple stores users.id (the primary key) and names.id (the primary key) as well as a timestamp. Here is where my problem lies. I want to show a \Table\Db of the users but also include their last used name from names. So to get this, you would select the login_name from logins ordered by timestamp desc and then take that ID and select name_unique that corresponds to that login. However, whenever I join the logins table, and then join the names table to get their name and show it on the table, it shows ALL of the users' logins and all of the names because it is not limited to only their last login. It joins ALL of their logins including all of the names they've used, including when they've used the same name multiple times. Is there a way to do a join and only grab the last entry where logins.user_id=users_id? I really hope this made any sense. It's such a hard thing to get into writing.
  14. Never mind this was completely user error, as usual. I accidentally got my Bot Token and Client Secret backwards.... twice. I guess I'm losing my mind after all.
  15. Hey @Ahmad E., hope you're doing well. I've got a quick question for you with a new error I just started getting out of no where. Uncaught Exception: IPS\discord\Api\Exception\UnauthorizedException: (0) discord_exception: array ( 'code' => 0, 'message' => '401: Unauthorized', ) Any idea what could be causing this? I tried just about everything including reinstalling the app and setting the bots back up with no luck. Just constant UnauthorizedException (401). I don't want to be that prick, but this is definitely kind of an emergency as such a large portion of my community relies on this sign-in method and can't access the website without it. Thank you!
×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy