JRay BinhQuang It would be cool if the Facebook and G+ share used the post content instead of the website description. It pulls in the post title but not the post detail.
JRay BinhQuang Done Awesome thanks! Can I update the extension via composer or do I need to remove/reinstall?
JRay BinhQuang composer require vingle/flarum-share-social Maybe if you update the version number then composer will pull the update?
JRay BinhQuang Oh ok. I'm still seeing "version": "0.1.0", in your json on Github here: https://github.com/tutula1/vingle-share-social/blob/master/composer.json
JRay I think you may need to re-tag it in Composer after making the change. I'm still not seeing the update via composer update. 🙂
JRay luceos JRay clicking update on packagist should be sufficient Good to know. I hope my friend @BinhQuang clicks it. 🙂
JRay BinhQuang maybe try releasing as 0.2.0? I'm not too familiar with Composer. Maybe @luceos knows better.
santiagobiali BinhQuang Version in composer isn't needed. just release a new version in github and update in packagist.
Franz santiagobiali update in packagist. ...which you can configure to happen automatically whenever you push a commit or a tag.
luceos Franz santiagobiali Maybe one of you should be more specific 🙂 Bottomline: Do not set a version attribute in the composer.json of your package, because it will overrule any other method of setting the package version (eg by pushing a tag to github). Releasing a new version on github is by pushing a tag to your repository: git tag 0.2.0 git push --tags If you want to have packagist automatically update your package: in your packagist.org profile click show api token copy the shown token in your github package settings page, click webhooks & services, add service. Search for packagist and click, under username fill in your packagist username, under token the previously copied token, leave domain empty ensure active is checked and add. C'est ca.
