Divio announced an end of support for Aldryn-forms at the end of September 2020. (http://support.divio.com/en/articles/3849075-essential-knowledge-django-addons-list).
I'm looking for add-on alternatives for Aldryn-forms that can work with the latest versions of Django, Django-CMS and Phyton.
On the marketplace website I only could find one package but its' last update was in 2015.
Does anyone knows a good package or has some information to implement forms which can be edited by content editors in the frontend website.
Thanks for any help.
Regards,
Carla
Divio handled over the maintenance to me, since I have commercial projects running on aldryn-forms.
Also Django CMS Association is most likely going to continue at least the basic maintenance of aldryn-forms, simply because the only alternative that I know of (djangocms-forms) has been dead for ~4 years, and the end users definitely need the forms support in django CMS.
In the future I hope to release a backward incompatible rewrite of aldryn-forms, since the current version has rather frustrating UX. Yet when that happens the respective announcement is going to be published on the aldryn-forms github.
Related
Team,
I am a beginner on site core 9.0. We have a requirement to migrate the existing MVC 5.0 application to sitecore 9.0. I am trying to build a POC first by having a basic mvc 5.0 web application having a login page.
May i know step by step process to migrate this to site core 9.0. I have tried all resources...(may be i have missed some) and i am confused.
Can anyone please guide me with proper links/information.
Probably the best way to start is by taking a brief introductory course into Sitecore to learn the terminology and how things are put together. There are also a lot of online resources to help you get started (Google "getting started with Sitecore").
Joining the community (like this one, the one on sitecore.stackexchange.com, Sitecore Slack, Community Forums) will put you in touch with a lot of developers who can help you through your steps as you move piece by piece.
Your particular question here is a little too vague to answer accurately. There are a lot of things that need to be done and it all depends on your scenario and your existing MVC application. It may be more helpful to ask specifics about a particular scenario you are migrating, with code examples, and what you have tried already.
You also need to think about what you are trying to migrate. Are you moving to run off of a Content Delivery server? Or are you building your MVC application to consume Sitecore as a headless application? Those would be two entirely different migration approaches.
I have not come across many people who have used a Graph DB(such as a Neo4j) with Django. Even though there exist ORMs such as Neo4Django, I am not too happy with these solutions as they are potentially buggy and have very late development cycle. What do you suggests are best solutions?
As of today, neo4django's latest commit is in July 2014. There seems to be bulbflow which mentions that it can be used from django. Its github link on their homepage is a broken URL. The only project I found linking bulbflow to django is https://github.com/theonion/django-bulbs , but it has a deprecation note to a broken URL. I just filed issue #338 requesting if they can provide a fixed link, and the developer clarified that it has been converted into a private repository.
This SO answer sheds some light and points mainly at py2neo. In the same SO question, there is another answer stating that django was designed with RDBMS in mind.
For alternatives to django as a web framework with neo4j as backend, this SO thread seems to be quite rich with options.
Funny enough, more search through duckduckgo.com led me to this blog post which is like a hello world example of using neo4j. It mentions neomodel (last commit 19 days ago), which links to django-neomodel (last commit 6 months ago).
I am trying to convert an old app-engine-patch project to use the out-of-the-box Django in Google app engine (without the "Cloud SQL" part, because I tried to set that up and it was a pain, and also required 'enabling billing' to try it out).
Are there good docs somewhere on how to write an out-of-the-box Django app on app engine? Possibilities seem to be:
appengine-patch. Old and unsupported since 2009.
google-app-engine-django. Deprecated since 2010.
django-nonrel. No longer supported by its original authors, last check-in is months ago.
Django with Cloud SQL. As I said, a pain to set up, and requires enabling billing to try.
You would think this question or this one or this one are duplicates, but the discussion on there is so old as to be useless.
I encountered the same problem when I recently developed a Django app for GAE. As far as I can tell, the easiest way is to use Django nonrel. The Google App Engine Django tutorial suggests this approach.
Now the second part of your question seems more geared towards long-term support of Django nonrel. You are correct that Django nonrel is no longer being supported. It looks like Google has an article on how to use Cloud SQL with Django, but they caution that Cloud SQL is experimental and subject to change.
Based on all of this information, you are left with a few options.
Use Django nonrel with the understanding that it may not be supported in the future. It is a risk, but the easiest solution if you want to get started quickly.
Use Google's Cloud SQL with Django with the understanding that it is experimental and subject to change.
Use Django, but do not use the ORM layer. This means you cannot take advantage of Django's admin site and a lot of 3rd party tools. This is the least risky if you are worried about long-term support.
I encountered the same difficulties as you. Anyways, as django-nonrel is no longer supported I chose going for Google Cloud SQL, since it has its free trial running until June 1, 2013.
All the current tutorials are for Django-nonrel so new tutorials are missing and setting up Django for Cloud SQL is not so obvious. That's why I decided to write this tutorial myself.
I'm looking for a django/oauth project which would allow for open authentication to at least Twitter and Facebook (other services would be a bonus). It appears there was a thread started by TIMEX in Febuary 2010 with a few different package recommendations.
Since it has been approximately a year and a half since the originator first posed the question, I'd like to ask again, hoping that time may have given to some more robust packages.
Some packages mentioned from the previous thread:
http://code.google.com/p/django-gigyauth - Last updated July 18, 2010
https://github.com/simonw/django-openid - Last updated Jan 12, 2010
https://github.com/uswaretech/Django-Socialauth - Last updated July 5, 2010
I think django-socialregistration is the most widely used. Check djangopackages for a more detailed overview of what is available.
I have to go with https://github.com/omab/django-social-auth. It's the best maintained and easiest to set up. http://djangopackages.com is going to that for authentication shortly. Why Because it rocks.
Yeah, I'm one of the people behind http://djangopackages.com. :)
Django Facebook is the most mature for Facebook authentication, it only does facebook though, none of the other systems.
If you are looking for additional platforms (and don't require additional facebook integration) than socialauth would work for you
Is there any chance that an application developed with Pinax could be deployed in Google App Engine?
As I know, Pinax is based on Django, and integrates tons of applications, it is suitable for building even a social networking site. It's extremely useful but I wonder if I can deploy it on google app engine.
Thank you,
The main issue here is that Django ORM is not compatible with GAE's datastore but some work has already been made to port Pinax using app-engine-patch. Here is the repository.
The key of course is JOIN support for the many to many model relationships. Since this is already being solved for 'eventual consistency' context, there should be no reason that we couldn't. I'm in the middle of moving the social demo over right now.
"Hoang"-
It looks like there was a release on Aug 2, 2009, to include Django 1.1 (see http://code.google.com/p/app-engine-patch/wiki/ReleaseNotes )
I know you said July, and August 2 isn't much different than July. :)
I, too, am interested in Pinax on App Engine. Please report your findings, if you try it!
Pinaxcombo does it only for the blog part of Pinax. Has there been any effort to port the 'entire' Pinax onto GAE?