I want to know about the cakephp 3.4 request cycle whether it is change or not according to previous versions of cakephp and please help me to understand cakephp request cycle easily.
Related
I'm testing Laravel Cashier for accepting Stripe payments. Everything is working, but still looks bad. I see in the docs that there is a 'cashier.payments' page that can be published so we can modify it to match our page. I'd love to use that, but I can't see how to use it. There's no existing route and without the code, I wouldn't know how to create one (it requires some parameters).
I tried php artisan vendor:publish --tag="cashier-payment" (based on the instructions for publishing the billing-portal), but the response was 'No publishable resources for tag'.
I've looked through the 'vendor/stripe' folder, but can't see anything like 'cashier/payments' that would help.
Has it been removed? Or does anyone know how to activate it?
We were using Apache Directory API 1.x and it was using the AdDirSyncImpl to send the cookies to the Microsoft Directory and receiving the reply cookie through AdDirSyncDecorator.
Now we are upgrading the Apache Directory API to 2.x and it seems the above APIs were removed from the latest one and instead of these API, they have introduced the new AdDirSyncRequestImpl and AdDirSyncResponseImpl and many others.
So, anyone has use these API, Kindly confirm that, do I need to replace the AdDirSyncImpl by AdDirSyncRequestImpl and AdDirSyncDecorator by AdDirSyncResponseImpl.
Thank you in advanced.
Documentation for DS.ActiveModelAdapter is exists only for 1.13 (for 2 - 404:
https://api.emberjs.com/ember-data/1.13/classes/DS.ActiveModelAdapter
So, it looks like it's moved out from DS:
https://github.com/ember-data/active-model-adapter
We have ember-data 2.13.2 and it's working fine with active-model-adapter
But we got some issues with the bump to ember-data 2.14.11 with nested behavior
The big issue here is to rewrite the backend part.
We also may use RESTAdapter:
https://www.emberscreencasts.com/posts/113-restadapter-vs-jsonapiadapter-vs-activemodeladapter
but it looks like ember way is JSONAPIAdapter way:
https://api.emberjs.com/ember-data/release/classes/JSONAPIAdapter
So, generally, the question is: what way is better for ember-upgrade?
keep backend API and maintain active-model-adapter
rewrite backend API and migrate to JSONAPIAdapter (with data/relationships approach)
rewrite backend API and migrate to RESTAdapter
keep backend API and implement custom serializer to change on the fly input/output to use JSONAPIAdapter or RESTAdapter (pick best) logic on FE (maybe it's some crazy way, but it's just to ask)
Note: backend API on RubyOnRails
A rewrite of your backend is not needed. Ember Data is flexible enough to handle all REST APIs that follow some convention among their endpoints.
Let's have a look on your specific use case.
ActiveModelAdapter and ActiveModelSerializer were deprecated in Ember Data 1.13 and removed in Ember Data 2.0. But the logic itself is still available through active-model-adapter package.
All that package does is providing a customization of Ember Data's build-in RestAdapter and RestSerializer packages. If you ignore the in-source documentation it's actually not much code. You can find it in the addon/ folder of active-model-adapter package.
So even if this package would not be available you could still customize RestAdapter and RestSerializer in the same way to support your backend as is.
I just installed Sylius and noticed that there are 2 backend sites. The installation documentation directed me to /admin. The site frontend has a link to /administrator.
What is the difference?
/admin is the original backend. /administrator is the new backend. See this article: http://sylius.org/blog/backend-redesign
There are also some differences in how products are created. When I created products in the old backend, it generated an error when displaying the product list in the new backend. I went back to the old backend, deleted the products and everything was fine again.
Nope, /admin is the new one,
Have a look at the last security config file here: https://github.com/Sylius/Sylius/blob/master/app/config/security.yml
/administration is part of the SyliusWebBundle which is no more used (https://github.com/Sylius/Sylius/pull/5535)
Does anyone know if you still need the sf404.aspx mapping for Sitefinity 4.4?
I'm trying to run a new test SF 4.4 project, but when I try and login the page just gives me the following:
HTTP 404 cannot find /sf404.aspx (this was mapped like that for Sitefinity 3.7)
I then changed the IIS 404 configuration from sf404 to default and now I just get HTTP/1.1 404 Object Not Found.
The project works through Cassini, but not through IIS 6.
Any ideas?
Regards,
Jacques
the sf404.aspx page is definitely only used for Sitefinity 3.x and should not be mapped in a Sitefinty 4 website.
If you are attempting to run a newer version of Sitefinity on IIS6, you need to make sure to use a wildcard mapping so that all requests go through the ASP.NET engine.
This page details everything you need to setup to run Sitefinity on IIS6: http://www.sitefinity.com/documentation/documentationarticles/installation-and-administration-guide/install-sitefinity/configuring-the-iis-to-host-sitefinity-projects
You might also find this blog post helpful: http://www.sitefinity.com/blogs/joshmorales/posts/11-02-23/installing_sitefinity_4_on_iis_6.aspx