Jump to content

Nathan Explosion

Clients
  • Posts

    7,012
  • Joined

  • Days Won

    128

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Forums

Events

Store

Gallery

Everything posted by Nathan Explosion

  1. What are your settings? I already know the answer but you providing your settings will allow me to explain it clearly for you.
  2. First post plus the next X amount of comments.
  3. Available when hiding all content only - will show the first post plus X number of comments.
  4. The '0' in 03:30 PM is redundant, due to the presence of PM - it should be either a) 3:30 PM or b) 15:30
  5. You should check the conf_global.php file in the root of your installation to determine which DB is used by your Invision installation - the 'sql_database' entry is the name of the DB used.
  6. Question: what is your minimum word limit? Reason for asking - I'm making a slight change to the code which might make your use-case a little easier to handle.
  7. Adding for later reference if/when adding new features... add ability to add and/or conditionals to the limits applied by the application.
  8. Ok...so no integration required in that case. I'll post this over in the support topic for the other app.
  9. You're going to have to elaborate. How exactly is any integration going to work, in your opinion?
  10. Answered in the support topic for the resource.
  11. @Markus Jung I don't use Blogs, so cannot develop for it - and purchasing it is a $100 outlay alone on my part. I can easily add a basic check to see if the user is in the Blogs application and have the functionality available there, however adding granularity to the permissions requires purchasing of the application so I can see the code. As noted in the information provided in the resource listing:
  12. Yes - you likely have your tasks set to use CRON (check that in the ACP), and the command line for your CRON entry needs to be updated to reflect the version of PHP you are using (check that on your hosting)
  13. If you are concerned that it begins a process, then it doesn't. Just click it, it brings you to a web page.
  14. A better first step is to download this, upload it to your server and then run it under the offending PHP version if it flags something as missing then action it (the most common issue is that the mySql extensions aren't enabled) - if not, then move in elsewhere in your troubleshooting
  15. Alternatively, instead of going down a rabbit hole on assumption of an email delay...bring up the developer tools in the browser, and see what is reported back when you click to submit. The action performed is an ajax request (because it is a reply, as opposed to a full form submit) and the normally expected result would be the content of what you submitted so that page then refreshes to show that. If an error is displayed (in the response to the submit) then work from there. If no error, then crack on looking elsewhere (such as an email notification delay)
  16. Pending approval at the time of creation of this post...
  17. v1.2.0 is currently pending approval FIXES Fixed issue where a member's badge choice is returned as NULL and potentially triggers a template error dependent on application settings (see note below) CHANGES Display of badges in postbit now excludes multiples of the same badge (see note below) Minor language updates NEW Added a setting to allow easy removal of the 'View badges' link in the postbit In account settings, list of available badge choices is order by chosen then unchosen, as opposed to previously being in badge order Note: referenced fixes/changes are made at template level - if you have modified any of the application's 4 template files then you should revert the changes to pick up the modifications.
  18. Go to the resource and click the indicated button: You'll get notifications as and when, and you can refer to the change log.
  19. And for those who would like the notice to only appear when the user is in breach of the criteria then the following added to your custom.css will take care of that - no new functionality needs to be added: #neapp_contentlimits_editorcount_display.ipsMessage_warning{ display:none; }
×
×
  • Create New...