Jump to content

Daniel F

Invision Community Team
  • Posts

    6,568
  • Joined

  • Days Won

    37

 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 Daniel F

  1. That’s an issue with a 3rd party app/plugin.
  2. It’s caused either by the size of the template or a specific variable inside the template, your host should be able to clarify this. I‘m also currently working on some improvements to the error handling to return a more useful error message in such a case.
  3. Daniel F

    Webhooks

    Webhooks allow your IPS community to communicate with third-party applications and websites. Unlike like the REST API where the data are pulled from your community by 3rd party services, webhooks will notify the other service immediately once the defined event occurred. 1. Firing a Webhook You can use the \IPS\Api\Webhook::fire() method to trigger the webhook in your code. This method accepts 3 parameters, where only the first one is mandatory. /** * This method will log the webhook to be fired, it's going to be fired via a task! * * @param string $event The event key * @param mixed $data Data * @param array $filters Filters * @return void */ public static function fire( $event, $data = NULL, $filters = array() ) So to fire a simple hook, you'll call: \IPS\Api\Webhook::fire( 'eventName', $payload ); This will register the webhook to the queue and it will be sent automatically with some minor delay ( something to keep in mind while testing your code!) 2. Registering the Webhook The Application::getWebhooks() method can be used to make IPS Community Suite aware of the available webhooks. The method has to return an array containing the available webhook keys and their payload. /** * Returns a list of all existing webhooks and their payload in this app. * * @return array */ public function getWebhooks() : array { return array_merge( [ 'myApp_eventKey1' => \IPS\gallery\Album::class, 'myApp_eventKey2' => ['test' => "array", 'member' => \IPS\Member::class] ],parent::getWebhooks()); } Additional to implementing the getWebhooks method, you'll also need to create language strings with following key pattern: webhook_myApp_eventKey1 which will be used for the description in the webhooks form!
  4. We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you. ( Your ACP login requires the email address, but we have only the member name on file)
  5. 1. There was actually a bug which caused that the warning was always shown, even when no promotion services were enabled. 2. You have no services enabled! The Twitter Promotion is set up, but it is disabled on your installation!
  6. Daniel F

    Mark Topic

    Some suggestions: There's no need for the Uninstall Extension because they're going to be automatically removed as long as they're correctly associated with the app. The part inside marktopic_hook_code_forums_modules_front_topic::manage would probably be better suited inside Topic::_setBreadcrumbAndTitle . Keep in mind that people could have more then one app/plugin with a hook overriding or adjusting the title. I would probably also use a better(unique) name for the _sendNotification method which is added to the existing class via a hook to not have to worry about any other plugin or we at IPS adding a method with the same name;) Same with the _deleteOldNotifications method. TBH, I would probably even move the 2 methods ( and everything else what's called inside the methods which are called direct via an action like the _checkAndSaveMarker method into the Topic Item class instead of the controller!
  7. I've tried to check your log but couldn't log in. Please ensure that the admin account which we have on file has permissions to access the ACP and view the system log.
  8. Is the code valid? What happens when you try to save an empty template or a template with a simple “hello” output? If it also fails, it’s probably your new server and I would contact the host to see if they’re using any WAF( web application firewall) which could be blocking the requests.
  9. Do you see any errors in your browser console?
  10. Daniel F

    Mark Topic

    Sorry, that was the wrong question, I'm not a fan of gingerbread🤷‍♂️😂
  11. Thanks, I have fixed this for an upcoming release. btw, it should be only <style>
  12. It's intentional that it's done this way to avoid that people like their own content with an alter ego account which would increase their reputation without really noticing where and why it was increased.
  13. The 4.6 version isn’t showing up because it wasn’t reviewed yet.
  14. Daniel F

    Mark Topic

    It wasn’t reviewed yet. There’s a really huge backlog from over the holidays which we’re cleaning up slowly.
  15. That’s a security feature within the IPS ACP.
  16. You can achieve the same with our IP.Pages application
  17. Make sure that the datastore directory is writable!
  18. We would need to look further into this for you, however the access details on file appear to be incorrect. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you.
  19. That's their documents api https://www.elastic.co/guide/en/app-search/current/documents.html for their app search service, which is something else! IPS is utilising their Elastic REST API which works as explained in https://invisioncommunity.com/forums/topic/464712-setup-elasticsearch-with-elasticco/?do=findComment&comment=2875516
  20. No, it's not needed.Here's what I'm using and which is working just fine: 1. As domain use the endpoint which you got from them. 2. constants.php needed 2 new constants: define('ELASTICSEARCH_USER' ,"elastic"); define( 'ELASTICSEARCH_PASSWORD' , YOURPASSWORD); where YOURPASSWORD is the one which you got while setup up everything ( you can reset it in the security section if you want an unique one for the elastic user)
  21. Try to add following 2 lines to your constants.php file: define('ELASTICSEARCH_USER' ,"elastic"); define( 'ELASTICSEARCH_PASSWORD' , YOURPASSWORD);
  22. Few instances were fixed, but this one was indeed missed. Thanks for the report @Gabriel Torres, I have fixed it for an upcoming release:)
×
×
  • Create New...