How to setup MichaelMackus/SyliusSubscriptionBundle in Sylius 1.3
I have already setup this repo
but I don't know how to make product subscribable from the admin dashboard.
This implementation is for Sylius v1.0, a lot has been changed now.
I want to see this work for either version of sylius.
I had a look into the bundle once and came to the conclusion that it never worked. I might be wrong but for sure I can say, it will not work for 1.3 because Sylius migrated to Symfony Flex.
It accesses properties which are not there nor will be implemented by the bundle like OrderItem::getSubscription() used here but is not defined.
There is an PR on Github to integrate this bundle into Sylius and takes care of the aforementioned issue but the PR is outdated as well.
I assume you have integrate Subscription on your own.
Related
I am using Symfony 6 and I should use CAS bundle for my app because we use SSO system. So, can I install the following bundle while I use Symfony 6 because there is no CAS bundle for Symfony6:
https://github.com/ecphp/cas-bundle
I asked Symfony Community and I got recieved this message:
Unfortunately, I've never worked with CAS protocol before, so don't
use those bundles myself. But let me give you some hints. First of
all, I see that the bundle you linked https://github.com/ecphp/ca...
does not support Symfony 6 yet, though there's an issue about it:
https://github.com/ecphp/ca... - feel free to follow it to know when
that issue is closed. Also, if you have time - feel free to help with
upgrading that bundle and make it compatible with Symfony 6 and send a
PR - that may have a good side effect, because even if the bundle is
slow on reviewing/merging your PR - you will be able to use your
fork in your project while PR is not merged yet. Other options - you
may want to take a look at GitHub search:
https://github.com/search?o... - probably you will find that is still
maintained. If no luck - you may want to use low-level tools that are
used in those bundles to write the implementation yourself - take a
look at composer.json file to see what libs are used behind the scene
in those bundles that might help you. Or, another option - downgrade
your project to Symfony 5.4. Basically, Symfony 5.4 == 6.0, but in
Symfony 6.0 just dropped all the legacy code since 5.x version.
Though, it might work and you will be able to install that bundle, but
keep in mind that if the bundle is dead and nobody will add Symfony 6
support there - you won't be able to upgrade to the newer version at
some point.
Do you have any idea about this issue?
Thanks all :)
It seems there is a CAS bundle for Symfony 6.
Take a look to
https://packagist.org/packages/l3/cas-guard-bundle
https://packagist.org/packages/l3/cas-bundle
I have a store running Prestashop 1.7.2.4 (with Symfony 2.8.27) with tons of customized files, theme, modules etc.. I just can't upgrade to newer Prestashop versions otherwise i will loose a lot of work in a blink of an eye.
My question is simple, can I apply prestashop version by version from 1.7.2 up to 1.7.8 security patches on my actual installed PS ? That is including Symfony vulnerable issues.
What is your advice.
Prestashop security patches applied over time are listed here , you should search the pull requests related to those advisiories and apply / cherry pick them manually on your release.
This can be a hard task though, especially from such an old version.
Generally, I suggest to move your core changes to modules / overrides so that you can update safely to latest version, so you can also benefit of PHP 7.4 support (note that themes and third party modules will not be overwritten during upgrade).
Some time after the release of Elm19 I published a library, which I needed for an Elm18 code base: thought2/elm-wikimedia-commons.
This worked well, it's listed in the community driven Elm18 package database: https://dmy.github.io/elm-0.18-packages/, can be installed and all good. Except the fact that the documentation is not shown in the package details, but that I heard is a known bug there. (But still I think this is very bad)
But the main problem is now, how to migrate the library to Elm 19: The actual migration steps are done and live in the master branch of the repo: http://github.com/thought2/elm-wikimedia-commons
The Elm18 versions proceeded to 1.1.0 in the meanwhile and after the migration there had to be done an API change, so I'd assume the latest version to become 2.0.0. If I add this to elm.json, the command elm publish tells me that this would be the first version and I should change this. Which is not right.
After a bit of research, I found out that the package (among other 18 ones that have been published in the same time period) is not listed in this json: https://package.elm-lang.org/all-packages This should contain all packages regardless of versions.
Any ideas what to do? This is really blocking my development, as I'm stuck in both lands now: 18 and 19. Would appreciate a lot if someone has some hints or solutions for me!
You shouldn't need to mess with the version number specified in elm.json.
If you set it back to the version of the package that is already published and run elm bump the elm program will look at the changes you've made to the package's API and set the new version accordingly.
Looking at https://github.com/thought2/elm-wikimedia-commons it doesn't look like any of your upgrade changes were breaking changes to your package API so the version won't be a 2.x.x, it will be a 1.x.x.
You'll need to remove the 2.0.0 git tag as well and instead add a tag for the version that elm bump tells you that your package is.
What are Sylius/Sylius-Standard and
Sylius/Sylius projects?
Installation guide leads to Sylius/Sylius-Standard and http://demo.sylius.org/ shows Sylius/Sylius-Standard.
So what is Sylius/Sylius?
Sylius Standard uses all the components as add ins (through composer). This means you'll build your app using the sylius components you want.
Sylius adds all the components to the src directory so you can modify the components yourself if you want to. It's a prebuilt app with the Sylius components already in there.
That's what i think anyway. I've been using the Sylius project for the last 6 weeks and it's been incredible. Was a steep learning curve as i was unfamiliar with symfony.
Sylius/Sylius - is Sylius CORE
Sylius/Sylius-Standard - is what you need for starting new project
Sylius/SyliusDemo - is prod example of Sylius DEMO
doesn't play framework 2.0.4 support some consoles?
when i was using 1.x, i could use the console "play eclipsify"
and "play dependencies" to fbconnect and fbgraph modules
but from when i chaged the version, it's not working.
then how can i connect those modules? i've no idea to do that
i think the new version doesn't support those consoles for modules
is it correct?
is the way totally different? if then please let me know.
also juz awhile ago i checked the 1.2.5 version
and there is no dependencies.yml and module folder
would you let me know what changed and how can i apply and adjust?
Thank you for your time
https://github.com/playframework/Play20/wiki/Play-2.0-for-Play-1.x-developers
check this out
and i wanna tell you some people who evaluate my question
what if there is no begginer who really want to learn and ask, how developing survives?
i hate reputations!
Yes, it's TOTALY different, although some ideas are the same, Play 2.x is quite new product (as stated in many topics and questions since many months), there's (fortunately) no backward compatibility between Play 1.x and 2.x!
When you'll visit Play 1.x (only) modules page the first thing you'll see will be that disclaimer:
These modules are for the Play 1.x series only. Play 2.0 modules can be hosted anywhere on any Ivy, Maven or Git repository. We will add a directory for them here shortly.
Thanx to Pere Villega you can also search for Play 2.0 for Java or Scala modules on PlayModules.net site, however you need carefully choose between Play 1.x and Play 2.x series.
For working with eclipse, check the Play's 2.0 IDE documentation.