Jump to content

Nathan Explosion

Friends
  • Posts

    7,136
  • Joined

  • Days Won

    129

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by Nathan Explosion

  1. We discussed that very issue above previously and the cause was the HTML used was malformed...and I expect it to be the same thing again. Provide the HTML you are inserting in to the content (via API, if I remember correctly)
  2. Right there in the search results information:
  3. ? I have literally told you what you need to do... Edit each of your themes Remove your chosen group from the 'Available for' field for those themes that you don't want your chosen group to use Add your chosen group to the 'Available for' field for the theme that you do want your chosen group to use
  4. In an attempt to get myself out of a funk with work on a different plugin, I've changed tack and decided to give this plugin some love - and I've taken a look at an interesting request that someone made at some point last year. A little taster of something which is coming in v2 of this, which will be retitled "(NE) Poll Enhancements": Forums - IPS 4.5.4 (B) - Development – Mozilla Firefox 2021-01-29 16-09-07.mp4
  5. v2.0.3 has been submitted for approval FIX: resolved issue where if the application is configured to affect topics in "Forum A" then it didn't affect comments being added to a specific topic in a different forum when the topic happens to have the same ID as "Forum A" FIX: resolved issue where if the application is configured to affect records in "Database A" then it didn't affect comments being added to a specific record in a different database when the record happens to have the same ID as "Database A" FIX: resolved issue where if the application is configured to affect events in "Calendar A" then it didn't affect comments being added to a specific event in a different calendar when the event happens to have the same ID as "Calendar A" Reminder for myself...next version, update the flipping screenshots!!!
  6. Now that I have taken a closer look at this, the actual issue is nothing to do with "...very large posts" The actual cause is the specific topic being viewed in "Forum A", which is not configured to be affected by the application's setttings, actually has the same ID as a "Forum B" which is configured to be affected by the application's settings. I'll have a closer look and an update will be out soon enough.
  7. v1.0.3 is currently pending approval: FIX: User/Group listing no longer displays an error after a user group has been deleted in the ACP CHANGE: Minor language string updates
  8. Edit all your themes except the 'barebone' one and disallow your group from using them. The edit that one theme, make sure your group is allowed to use it. Result: only allowed to use one theme.
  9. Send me: 1) a link to your site 2) login credentials to access the site. 3) ALL your settings page, not just the one you provided.
  10. To help people in a constructive manner... Go in to your client area and click the 'Manage this purchase' button Then click the 'Create request' button: Or the '? Support' button in the bottom right corner: The result: Want to see previous cases? Click the 'Previous conversations' link near the bottom there.
  11. Something I've brought up previously in the Contributor Chat forum, but it drifted off into the ether...never to be seen again. I've recently gone back to the POC for something, and this behaviour is still there and it's frankly nonsense. Background: there is something in the POC application which will be relying on the order of entry being kept 'as is' as the setting is going to be used later to display things in the chosen order. My settings code - nice and simple, it works... //<?php $form->add(new \IPS\Helpers\Form\Item('tids', \IPS\Settings::i()->tids, TRUE, array('class' => '\IPS\forums\Topic'))); if ($values = $form->values()) { $form->saveAsSettings(); return TRUE; } return $form; Result, pre-save (note the order for the topics is 2,3,1) Save the form - result (note the order for the topics is now 3,2,1) The issue is that when the above form is saved, the fields values are sorted in DESC order based on the topic ID. Dumping the $values/$form->values to the screen immediately upon the Save button being clicked shows that the sort has already taken place before the 'saveAsSettings' has been processed. I can't see anything that will allow me to specify NOT to do the sort, so any chance that something can be added in? I've got a workaround to this in my application, which involves using a different form in a dialog to add a single item to an existing list of topic IDs which works but feels clunky.
  12. Removed cos' he can't do what I suggested...
  13. Incorrect - Dynamic row format is a per-database feature; he probably thinks you have asked for the default setting for new tables on the server to be set to Dynamic. Read this topic:
  14. I've got a few ideas already in this area, but I will add in a "Notes" field to allow you to put some information in. But this... I am keeping the field id as the first column. Placeholders are text only - no html. There are CSS tricks out there though, and I will have a think about how they can be implemented (there are NO promises that this will be implemented)
  15. Define 'Data' - are you referring to file system? Content on the site? Applications? Plugins?
  16. What's new in v2.0.2 (pending approval at the time of this post) CHANGE: Modified the settings page to improve the display of group tabs for administrators who have a large number of groups on their site.
  17. Then turn it off, if you haven't already done so.
  18. This evening's 'Pointless notification' is brought to you by Paul E, again.
  19. Go in to the ACP - type it in to the search bar...
  20. It is not possible to add a placeholder in to the Editor, that is what I have said above. This is the Editor:
  21. Log a ticket with support
  22. I'm taking a look into this one at the moment - for reference, the grey text you are referring to is known as a 'Placeholder' and it can be added to some HTML input fields but not all. For example: The "Title" field is a text input - it accepts the placeholder attribute: However, the "Message area" is an Editor generated by CKEditor and it doesn't currently have a placeholder attribute which can be manipulated in the same way as other inputs can.
  23. Then turn off "Post before registering"
×
×
  • Create New...