This link https://developers.google.com/appengine/docs/python/tools/libraries27 suggest "1.5" & "Latest" but doesn't exactly specify 'Latest'. Also, who knows when was this document updated. If any of you guys have been deploying your apps on GAE, please let me know.
The SDK release notes contain this information.
https://code.google.com/p/googleappengine/wiki/SdkReleaseNotes
Django 1.5.4 has been upgraded to 1.5.8.
So currently looks like 1.5.8 is the latest. Where there might be a central list of what version you can use if you want I don't know.
Related
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.
I am trying to use a payment module in OpenCart version 2.0.1.1, and I need to update our Hash to HMAC-SHA-512, so the checkout page authorizes successfully.
I just don´t know how to change the hash and where exactly I can do this.
We use Plesk, with PHP 7. The domain is www.didikong.de
The payment module is WireCard Checkout Page version 1.2.0.
So this wirecard generates a Fingerprint, which is encrypted via HMAC-SHA-512. And our website uses SSL.
Thanks in Advance.
I am really not sure if the version 1.5.2 of opencart-wcp was still compatible with 2.0.1.1 but I would try that first. There was a client library update between 1.2.0 and 1.5.2 in which the algorythm was updated. If you don't have a test system where you could try it out just check the changes in the client lib. More in particular look into the /system/library/wirecard/vendor/wirecard/checkout-client-library/library/WirecardCEE/QPay/FrontendClient.php file and see if the setHashAlgorithm is using the WirecardCEE_Stdlib_Fingerprint::HASH_ALGORITHM_HMAC_SHA512 constant. If not, just change it to the mentioned constant and you should be good to go. If you get any errors regarding some missing things consider updating the /system/library/wirecard/vendor/wirecard/checkout-client-library/library/WirecardCEE/Stdlib/Client/ClientAbstract.php to the newest version.
I have access to our corporate PCF, though both the Apps Manager webpage and the "cf" CLI (and thus the API).
How can I detect what version of PCF they're running? There's nothing in the website that lists it, and the best I can find is using cf api which returns:
api version: 2.98.0
How can I map that to the PCF version, or is there another way to detect it?
Usually via Ops Manager however another quick way is to click on the 'Docs' in Apps Manager it should take you to the documentation of relevant PCF version. For ex: https://docs.pivotal.io/pivotalcf/2-6/pas/intro.html means PCF 2.6
Please be advised that documentation link requires to be updated during upgrades so if someone doesn't do - it will be pointing out to older version..
I don't believe Apps Manager or the API (i.e. Cloud Controller) will report that information. Both are just single parts of the entire system, so I think you could really only expect them to publish their own version information.
If you want to see versions of what is installed, you need to look at Ops Manager. That will show you the tiles that are installed and each version.
If you don't have access to Ops Manager, you'd need to ask your platform operators.
Hope that helps!
As of this year Django core devs removed docs for Django versions older than 1.7 from https://docs.djangoproject.com/.
Unfortunately, there’re still apps using older Django versions in the wild, such as the project I’m currently busy upgrading.
Googling variations of “django 1.5 docs” gives links to unfamiliar domains such as django-doc-test1.readthedocs.io and django-document-tchinese.readthedocs.io, and a PDF under media.readthedocs.org.
I’m looking for hosted navigable Django 1.5–1.6 documentation, preferably in HTML, is that still a thing? Any options apart from building the docs myself from source?
The docs for Django 1.4, 1.5 and 1.6 were removed from the official docs.djangoproject.com site in February 2016. See this discussion on the django-developers website for more details.
You can still view the docs for Django 1.4 and later on readthedocs.
For earlier versions of Django, you can view the source files on GitHub (for example, Django 1.3), but if you need html versions, you'll have to try building them yourself.
I want to create a web app using Django 1.5 or 1.6 using appEngine. I have read about as I have to do it and I have read about Django-nonrel which is very usefull to avoid the issues related with non-relational Database. Unfortunately I have read about the origininal creators project and they have left the project:
GoodBye
However I have seen new avaiables versions of Django AppEngine wich allow to use the 1.4 and 1.5 versions of Django
https://groups.google.com/forum/#!topic/django-non-relational/I06693ZPeME
After I have read every text I am a mess, do anyone redomended me use last version of django non-rel? can I use other framework? don't I use the last verion of Django?
Thank you.
I have developed a fairly complex web app using "normal" Django, not the non-rel flavour. For database storage I use Google Cloud SQL which is basically MySQL in the cloud. It works pretty good. There are some points to consider:
Google Cloud SQL has no "free plan", so it will incur a cost on your project.
Normal Django for GAE is currently at version 1.4 and lags a bit behind development which is if memory serves me right at 1.6. There is a version 1.5 of Django that comes with the GAE SDK but I did not get that work (I did not put any particular effort in it, just changed the Django version in my app.yaml file and it crashed).
As for the first bullet, there's now also a comparable product available from Amazon. I have not yet looked into it (I believe they do offer a free plan which might be interesting to try out), nor compared prices but that might be an alternative should Google Cloud SQL be too expensive. My yearly cost for Google Cloud SQL are between £150 and £200 which is not too bad.
My reason for choosing normal Django over non-rel was basically twofold:
The non-rel project appears abandoned.
The non-rel product is "crippled" in functionality according to some of the docs I read about it and you will not be able to use all of the pre-baked goodies of Django.
I have been working on this project for 7 months now and I find Django on GAE with Google Cloud SQL very stable and productive environments. FWIW, I use PyCharm which has a one click deployment feature which makes deploying my product an absolute breeze. I've been working on IT projects with various technologies for quite some time and the combination of PyCharm, Python, Django, GAE and Google Cloud SQL would be at the top of my list of productive environments.
Of course there are other Python frameworks to consider, like Flask which allow more of a best-of-breed approach but I have no experience with them.
Hope this helps.
I'm using django-nonrel 1.4, though I haven't updated to the latest build yet. It's running smoothly for me.
You do need to recognize that if you use django-nonrel, you have to live by the rules of the GAE HRD, especially the eventually consistent results, and the limited query capabilities.
Django-nonrel is definitely not abandoned! I am using the 1.6 version with much success at Docket Alarm and it is still being actively maintained.
Here are the up-to-date links to the project:
Docs
GitHub
Discussion group