We want to convert the pptx file like the below URL. My client already using some other tool. He wants to convert a presentation like a below conversion url. Please let me know laravel 8 support the package
@Pravins,
Thank you for the query. It will take me a while to understand your requirements. I will answer you later.
Documents: Convert PowerPoint Documents to other File Formats
@Pravins,
I don’t understand how Laravel 8 related to the issue. It seems you need a feature to convert presentations to HTML with slider representation instead of a long web page. Could you confirm it, please?
In the below url mentioned Aspose was supported Laravel Framework = 4., Laravel Framework = 5. But currently, we are working on the Laravel Framework 8. So it was not supported Laravel 8.? can you please check it and shared your input.
@Pravins,
I logged the issue in our tracking system with ID SLIDESCLOUD-1184. Our development team will check it. I will inform you about any progress.
You can check the below documentation for php.
I think this will work for laravel too.
Reference Links
Available SDKs|Documentation
GitHub - aspose-slides-cloud/aspose-slides-cloud-php: PHP library for communicating with the Aspose.Slides Cloud API
@mohantsi,
Welcome to our community! Thank you for the help.
Unfortunately, our developers have not tested Laravel 8 support yet. I’ve requested plans for this issue from our development team. We will inform you as soon as possible.
@Pravins,
Our development team has researched Laravel 8 support. There is no special support for Laravel 8 in Aspose.Slides Cloud SDK for PHP. But this does not mean that you can not use Aspose.Slides Cloud SDK with Laravel 8. The SDK is an ordinary PHP package, so it can be used with Laravel 8 just as any other third-party packages. It’s pretty simple, and we don’t think the extra wrapper will make it much easier to use the SDK.
However, we found one issue about using the SDK with Laravel 8. Laravel 8 requires GuzzleHttp 7.0.1 whereas Aspose.Slides Cloud SDK currently uses 6.2 version. We hope to fix this in v22.1. So far, to avoid conflicts, you have to downgrade GuzzleHttp to v6.2, i.e. in your composer.json replace “guzzlehttp/guzzle”: “^7.0.1”, with “guzzlehttp/guzzle”: “^6.2”.
You can check out a simple demo application:
UPD
Moving to Guzzle 7 would require a PHP version not less than 7, and our customers do use earlier versions. So, we would prefer to avoid moving to Guzzle 7.
Thus, a workaround becomes the solution - you have to downgrade GuzzleHttp to v6.2, i.e. in your composer.json replace “guzzlehttp/guzzle”: “^7.0.1”, with “guzzlehttp/guzzle”: “^6.2”.
If this option is unacceptable please inform us, and we will look for a more appropriate solution.