Caches can contain things that would cause them to break after a cache ﬂush in rare situations. Solution Usually this is not a problem and persisting sessions through cache ﬂushing is in most cases safe to do.
Google Analytics account, payment gateway options, email settings, web service settings, etc. Solution Use diﬀerent Flow sub contexts to diﬀerentiate between them. Example “Conﬁguration/Production/Testing/Settings.yaml” “Conﬁguration/Production/Live/Settings.yaml” “FLOW_CONTEXT = Production/Live”
multiple sites (easier to maintain) b) Use individual site packages for each site, but inherit conﬁguration/resources (more customizable) Good to know: • Only use with same conﬁguration across sites • No linking across sites (yet) • Basic access restrictions coming in 2.0 Follow progress at https://jira.typo3.org/browse/NEOS-177
the transition and make it possible for the editors to help with the migration. This can be done by allowing editors to add a the old URL for page to be redirected from. To do that you can use the MOC.Redirect Neos package which adds a ﬁeld to every page for entering the old URL https://github.com/mocdk/MOC.Redirects composer require "moc/redirects" "1.0.*"
custom package to handle payment gateway callback Plugin creates the form using a custom form factory Form displays a conﬁrmation page and handles validation and if passed redirects to the payment gateway with a custom form listener that stores the form information The plugin handles the returning customer A custom controller is used to capture the payment gateways callback and stores the payment information and processes the order through a signal
including form and conﬁrmation Resources/Private/Template/Donate/Finish.html • Template that shows success message Resources/Private/Template/Donate/PaymentCancelled.html • Template that shows cancelled message Resources/Private/Template/Donate/PaymentFailed.html • Template that shows failed message
form with validation Classes/Form/Finishers/DonateFinisher.php • Form ﬁnisher – store donation information, redirects to payment gateway Classes/Listeners/DonationTransactionPostProcessor.php • Finalize payment – send emails
web server according to standards Solid presets can be found for Apache, Nginx and others from the HTML5Boilerplate project https://github.com/h5bp/server-conﬁgs Alternatively use PageSpeed module from Google https://developers.google.com/speed/pagespeed/module
require "moc/imageoptimizer" “dev- master” (development version) Optimizes jpg, png, gif and svg images automatically. Supported platforms Linux, FreeBSD, OSX, SunOS & Windows + more with global binaries. Works for all Flow installations.
cache proxy like Varnish or Nginx static cache Example: Using Varnish requires sending cache-control headers with the HTTP responses To make that easier you can use the MOC.Varnish extension https://github.com/mocdk/MOC.Varnish (http://goo.gl/fGSAU9) However it’s still a rough proof-of-concept, but will be improved within the next few months to work perfectly together with Neos