Jump to content

Martin A.

Clients
  • Posts

    4,230
  • Joined

  • Last visited

  • Days Won

    21

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Martin A.

  1. I'd like to bump this (excuse me if there is another topic about this).
  2. Who should we report it to? If you google the link, and click the same link in the search result, you're still redirected to the same site. EDIT: Tried a different browser, one that's never been used on this forum, and that worked :blink:
  3. HTML can be used. You don't have to enable it somewhere, just add the HTMl to the rules.
  4. They've done that for previous point releases. Guess they didn't upload that for the same reason why as the upgrade packs.
  5. Most new features IPS put in a new release, seems to be based on the popularity of the suggestions. How can they measure it if there aren't a topic about it? No one is going to shoot you for suggesting something "dumb". If someone like the idea, they will reply, and support the suggestion, and then increase the possibility of that being a new feature.
  6. It's not so difficult, really. I did something similar in an application. If I disabled the whole app, it also disabled the hook. You should be able to do the same, only you have to recache the templates when you're done. And it also a bit friendlier for the user, than having to enable/disable hooks. Didn't I suggest that in the early beta stages? EDIT: No I didn't. I reported/requested that several hooks could share the same source file. http://forums.invisionpower.com/tracker/issue-13213-several-hook-points-cant-share-the-same-file/
  7. Can't you make a new setting (probably separated from the core settings system) where you make a lit of pre-defined locations, and update the hook data upon save, and recache the templates?
  8. $this->DB->build( array( 'select' => 'm.sys_module_key, m.sys_module_title, m.sys_module_application', 'from' => array( 'core_sys_module' => 'm' ), 'order' => 'a.app_title ASC, m.sys_module_title ASC', 'where' => 'm.sys_module_admin=0 AND m.sys_module_visible=1', 'add_join' => array( array( 'select' => 'a.app_title', 'from' => array( 'core_applications' => 'a' ), 'where' => 'a.app_directory=m.sys_module_application', 'type' => 'left' ) ) ) ); $this->DB->execute(); $modules = array(); $modules['all'] = "All modules"; while( $r = $this->DB->fetch() ) { $modules[ $r['sys_module_application'] . '::' . $r['sys_module_key'] ] = $r['app_title'] . ':: ' . $r['sys_module_title']; }
  9. #show_topics# would be better/worse/w/e :P I think #show_modules# will benefit those who make hooks that are restricted to certain sections on the board. Global Forum Message and IP.Shoutbox, just to mention a some.
  10. How about a #show_modules# too, while you're at it?
  11. Highly unofficial, but I think they only have ibresources.ru.
  12. Isn't there a link where the skin chooser should be, to over-ride the automatically assigned skin?
  13. I was thinking in lines of this. Lets say you have the following foreach block <foreach loop="$posts as $post"> /* Do the template parsing stuff here */ </foreach> When that's parsed from IPB HTML logic to PHP, if would be this foreach( $posts as $post ) { $post = $this->lookForForeachHooks( $post ); /* Do the template here */ ] Then lookForForeachHooks() would look for hooks used in foreachs, and pass $post to a function in that hook while it's iterating trough $posts.
  14. Or perhaps just do something with foreach template hooks. For each iteration, do something that triggers the hook, and pass the same data used in foreach() to getOutput(), or something.
  15. I doubt it. Since they actually have to support these releases, I think they'll update on Tuesday. If they release it on a Thursday or Friday, they'll get a huge backlog of support tickets and bug reports. Instead of letting it soak here over the weekend, and do the final finishing touches on Monday, and release it the next day.
  16. Bumpy-bump! How about a class in coreExtensions.php, or a new file to handle this?
  17. If this works in the same way it did in 2.3, new templates will be inserted to the master skin, and the skins will inherit from that. Once you've made changes to the template, it's nailed to that skin.
  18. I were gonna say she's named Rikki. But she's on the other side :P
  19. Nope, I was actually looking for that laptop girl everyone's referring too. Guess I'll never get to see her ever :(
  20. I don't like it being there. It's not relevant to the post, and not something I need to know about everyone. If I want to see more info about a member, I view their profile. It should either have an on/off switch, or be completely removed.
  21. Storing three revisions will in worst case scenario triple the size of ibf_posts, which already is the largest table.
  22. I'd like to request something similar like settings evalPHP for applications. As it is now, all apps with a public title is shown, no matter if the user has access to it or not. A field for raw PHP code could "solve" that. $show = 1; if ( ! in_array( $this->memberData['member_group_id'], explode( ',', $this->settings['theseHaveAccessToIt'] ) ) { $show = 0; } And, a checkbox to completely hide the application from the main navigation, allowing us to make UCP-only applications, and similar.
  23. Guess this could be done in the same way it works in IDM. When you click "Add file", you're asked to enter/verify the category you're about to post a file in. If that's done before the actual posting screen is shown, the issues Michael pointed out would be gone.
×
×
  • Create New...