GithubHelp home page GithubHelp logo

vormkracht10 / laravel-open-graph-image Goto Github PK

View Code? Open in Web Editor NEW
57.0 3.0 2.0 214 KB

Dynamically create Open Graph images for your website

License: MIT License

PHP 75.31% Blade 24.69%
laravel open-graph laravel-opengraph social-graph open-graph-protocol social-media

laravel-open-graph-image's People

Contributors

baspa avatar dependabot[bot] avatar github-actions[bot] avatar markvaneijk avatar sweptsquash avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

laravel-open-graph-image's Issues

Retrieve file path?

Hi,

First of all, thank you for this very useful package!
Is it possible to retrieve the image via File Storage? In particular, to be able to use the twitter API with the image generated by laravel-open-graph-image.
It would be necessary to be able to force the generation of the image and then retrieve the image path.

Thanks

403 forbidden on image show

Hi all,

We are currently using this package to generate custom Open Graph images in combination with Inertia.js SSR. The package works on my local environment, but deploying this package to AWS via Laravel Vapor, the generated URL gives me 403 Forbidden.

URL: https://cargopilot.com/open-graph-image?button=Register%20now&subtitle=Book%20air%20cargo%20in%20real%20time%20with%20CargoPilot.&title=CargoPilot&signature=aad87fb268df30f111e35d26acd03d8573f29421189ead5ff6390f769a25521c&.jpg

I have installed open-graph-image via php artisan. Did I miss anything in my setup?

Kind regards.

Error when accessing generated previews

I have just installed the library according to documentation, but the url in og:image returns laravel error page with this error:

The command "PATH=$PATH:/usr/local/bin:/opt/homebrew/bin NODE_PATH=npm root -g node '/var/www/html/vendor/spatie/browsershot/src/../bin/browser.cjs' '{"url":"file:///tmp/1418125068-0702841001699025455/index.html","action":"screenshot","options":{"type":"jpeg","quality":80,"args":["--no-sandbox"],"viewport":{"width":1200,"height":630},"displayHeaderFooter":false}}'" failed. Exit Code: 1(General error) Working directory: /var/www/html/public Output: ================ Error Output: ================ �[1m�[43m�[30m Puppeteer old Headless deprecation warning:�[0m�[33m In the near future headless: true will default to the new Headless mode for Chrome instead of the old Headless implementation. For more information, please see https://developer.chrome.com/articles/new-headless/. Consider opting in early by passing headless: "new" to puppeteer.launch() If you encounter any bugs, please report them to https://github.com/puppeteer/puppeteer/issues/new/choose.�[0m Error: Could not find Chrome (ver. 119.0.6045.105). This can occur if either 1. you did not perform an installation before running the script (e.g. npm install) or 2. your cache path is incorrectly configured (which is: /home/sail/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration. at ChromeLauncher.resolveExecutablePath (/var/www/html/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:298:27) at ChromeLauncher.executablePath (/var/www/html/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:204:25) at ChromeLauncher.computeLaunchArguments (/var/www/html/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ChromeLauncher.js:97:37) at async ChromeLauncher.launch (/var/www/html/node_modules/puppeteer-core/lib/cjs/puppeteer/node/ProductLauncher.js:79:28) at async callChrome (/var/www/html/vendor/spatie/browsershot/bin/browser.cjs:92:23)

[Bug] Pest is not working

Currently tests cannot be written because Pest does not seem to be configured correctly. When using a Facade for example the tests fail due the following error:

A facade root has not been set.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.