Re: How to create an individual instagram message into threads?

['Steven Mapes' via Django users]

I've not used that app but creating email of messaging chains is quite 
easy. How I normally do it is to generate a unique identifier by using a 
uuid4 plus some custom values when a new thread/conversation is created and 
then this is passed and maintained during replies.  There's probably 
something similar in that app. Emails tend to call it a Conversation ID

On Sunday, 27 August 2023 at 22:19:46 UTC+1 Ram wrote:

> Hi,
>
> We are using Instagram clone messaging in our ecommerce application where 
> users contact each other about market place item (sell/buy items). Once the 
> messaging started between two users on an item
> 1. we want to keep the further messaging regarding that item to be 
> continued like an email thread so that all the messaging about that item 
> will be in one thread.
> 2. New messaging on new market place item will be again new thread.
> 3. It would be nice each thread has a title of the market place item so 
> that same users can go back to previous history of messages on that 
> particular item whenever they want.
>
> I'm wondering whether anyone has implemented the above features using 
> instagram clone in your Django application?
>
> Best regards,
> ~Ram
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/099349c1-bfc4-42e8-8178-50141c7640d0n%40googlegroups.com.

Re: Slow Performance of Django Web App

['Steven Mapes' via Django users]

To start with I'd look at upgrading the project to the latest version of 
Django and Python as Python 3.10 and 3.11 have some performance 
improvements and you'll need to be on a Django 4 version to support them.

That aside it sounds like you've got good caching architecture setup  since 
it's working well when cached but that the architecture without the caching 
is not up to the job. You need to investigate where the performance hit is 
coming in, most likely it'll be database performance. Once thing to check 
would be whether you are using things like like prefetch_related, 
select_related, and defer with any queryset or are you always returning the 
whole object. If you are returning the whole object do you need to? 

After that it depends on how you are using and exposing Django as to what 
I'd suggest you check next. Are you using DRF as API backend to the pages 
in S3 or are you serving pages via Django and then caching those?  If it's 
the latter, run it locally with caching turned off and debug toolbar 
installed and look at each pages output to see how many queries you are 
hitting per page and the performance of each.

Since you are using a lot of caching how are you maintaining the cache? Are 
you letting it expire and then self populate or are you using warm-ups to 
fetch the update information and then update the cache prior to it 
expiring? If you're doing the former but the latter fits your setup look to 
switch to that. In those instances you can update the fetch the results to 
update the cache outside of a user transaction

On Monday, 12 June 2023 at 06:23:06 UTC+1 Kunal Mittal wrote:

> Hi, we are using Django 1.8.5
> Architecture is like -  Nginx side car -> wsgi server (gunicorn) -> 
> application
> On Monday, June 12, 2023 at 1:06:18 AM UTC+5:30 Mz Gz wrote:
>
>> What server do you use ?
>>
>> On Sun, 11 Jun 2023, 10:00 pm Kunal Mittal,  wrote:
>>
>>> I've a django application serving 10k+ users daily, that application has 
>>> everything to be on the top of performance metrics but still some API's 
>>> have high latencies, application serves lots of pages with nice css and 
>>> various images, on most the pages they are being served by s3 while on some 
>>> it's via django static files. We have implemented caching on akamai for 
>>> every static file that application serves, whenever that cache disappears 
>>> latency of each and every API spikes exponentially, at that time even 
>>> loading metrics becomes a pain, server does not pick those requests. Can 
>>> anyone suggest what's going on here. 
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to django-users...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/django-users/d32868ba-a2df-41e3-8f41-3ecc3c1b3471n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/c5e4d83c-1891-4005-939e-8c0f3f074cf2n%40googlegroups.com.

Re: how to convert to Django 3 or 4

['Steven Mapes' via Django users]

Ah Python 2.7, you'll need to upgrade through to at least 3.8 so unless 
it's a huge project where you have time to upgrade through the Django 
Versions and different versions of Python as you go, you may just want to 
create a new project and lift the code as you go.

On Friday, 9 June 2023 at 15:29:47 UTC+1 Rogerio Carrasqueira wrote:

> I'm using python 2.7, wich your suggestion?
>
> Thanks
>
>
> Rogério Carrasqueira
>
>
>
>
>
> Em sex., 9 de jun. de 2023 às 03:37, 'Steven Mapes' via Django users <
> django...@googlegroups.com> escreveu:
>
>> If you want to go directly then start a new project and "lift and shift" 
>> code fixing and updating as you go. Depending on the size of the project 
>> and the complexity of the processes it may be the fastest way to do it.
>>
>> If you want to keep the same project then upgrade in stages. The fact 
>> you're in 1.4 will make it hard and you'll need to do a lot of manual 
>> changes to get into 1.8 so starting new may well be quicker. If you did 
>> upgrade then I'd go 1.8 to 1.11, 2.2, 3.2 and finally 4.2.
>>
>> Branch the code using version control and see how bad it is but it'll 
>> depend on the project.
>> I went from 1.11 to 3.2 in a day for one but most of the code was bespoke 
>> without may external packages to worry about. Those could also cause you 
>> issues.
>>
>> Since the code is Django 1.4 what version of python is it also using?
>>
>>
>> On Thu, Jun 8, 2023, 21:31 Rogerio Carrasqueira  
>> wrote:
>>
>>> So just to undersand, I cannot move directly from 1.4 to 4 I have to do 
>>> it in steps, right?
>>>
>>> Thanks 
>>> Rogério Carrasqueira
>>>
>>>
>>>
>>>
>>>
>>> Em qui., 8 de jun. de 2023 às 17:01, 'Steven Mapes' via Django users <
>>> django...@googlegroups.com> escreveu:
>>>
>>>> I've used it to go from Django 3 to 4 and to move a project from 1.11 
>>>> to 2.2.
>>>>
>>>> It doesn't do everything for you but it's a great start. I've 
>>>> personally moved from 1.8 through to 4.2.2 but that was during their 
>>>> development lifecycle. Moving up to 1.7 and then 1.7 to 1.8 and 1.8 to 
>>>> 1.11 
>>>> and 1.11 to 2 will be the hardest parts but it'll get easier once you're 
>>>> on 
>>>> 1.11
>>>>
>>>> On Thu, Jun 8, 2023, 19:58 Rogério Carrasqueira <
>>>> rogerio.ca...@gmail.com> wrote:
>>>>
>>>>> Hey Steven!
>>>>>
>>>>> Thanks for this information, do you have tried it before? I would like 
>>>>> to move from 1.4 to lastest, do you think that is it possible?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Em quarta-feira, 7 de junho de 2023 às 11:52:35 UTC-3, Steven Mapes 
>>>>> escreveu:
>>>>>
>>>>>> I'd suggest looking into using Adam Johnson's Django-Upgrade told -
>>>>>> https://github.com/adamchainz/django-upgrade it will help you move 
>>>>>> between versions
>>>>>>
>>>>>> On Tuesday, 6 June 2023 at 15:24:36 UTC+1 Paul Haguet wrote:
>>>>>>
>>>>>>> There is a lot of function who can change. 
>>>>>>>
>>>>>>> https://docs.djangoproject.com/en/4.2/releases/4.0/
>>>>>>>
>>>>>>> All the function declared as deprecated into Django 3 has been 
>>>>>>> removed into Django 4. In the deprecated section of django 3 new 
>>>>>>> functions 
>>>>>>> names are systematically indicated. So just search the function under 
>>>>>>> their 
>>>>>>> old name and replace them with their new name. The 2 links below give 
>>>>>>> the 
>>>>>>> list.
>>>>>>>
>>>>>>>
>>>>>>> https://docs.djangoproject.com/en/4.2/releases/3.0/#deprecated-features-3-0
>>>>>>>
>>>>>>> https://docs.djangoproject.com/en/4.2/releases/3.1/#deprecated-features-3-1
>>>>>>>
>>>>>>> Le samedi 3 juin 2023 à 10:10:31 UTC+2, Shams Ulhaq a écrit :
>>>>>>>
>>>>>>>> Just need to change url import 
>>>>>>>>
>>>>>>>> from django.urls import include, re_path as url
>>>>>>&g

Re: how to convert to Django 3 or 4

['Steven Mapes' via Django users]

If you want to go directly then start a new project and "lift and shift"
code fixing and updating as you go. Depending on the size of the project
and the complexity of the processes it may be the fastest way to do it.

If you want to keep the same project then upgrade in stages. The fact
you're in 1.4 will make it hard and you'll need to do a lot of manual
changes to get into 1.8 so starting new may well be quicker. If you did
upgrade then I'd go 1.8 to 1.11, 2.2, 3.2 and finally 4.2.

Branch the code using version control and see how bad it is but it'll
depend on the project.
I went from 1.11 to 3.2 in a day for one but most of the code was bespoke
without may external packages to worry about. Those could also cause you
issues.

Since the code is Django 1.4 what version of python is it also using?


On Thu, Jun 8, 2023, 21:31 Rogerio Carrasqueira <
rogerio.carrasque...@gmail.com> wrote:

> So just to undersand, I cannot move directly from 1.4 to 4 I have to do it
> in steps, right?
>
> Thanks
> Rogério Carrasqueira
>
>
>
>
>
> Em qui., 8 de jun. de 2023 às 17:01, 'Steven Mapes' via Django users <
> django-users@googlegroups.com> escreveu:
>
>> I've used it to go from Django 3 to 4 and to move a project from 1.11 to
>> 2.2.
>>
>> It doesn't do everything for you but it's a great start. I've personally
>> moved from 1.8 through to 4.2.2 but that was during their development
>> lifecycle. Moving up to 1.7 and then 1.7 to 1.8 and 1.8 to 1.11 and 1.11 to
>> 2 will be the hardest parts but it'll get easier once you're on 1.11
>>
>> On Thu, Jun 8, 2023, 19:58 Rogério Carrasqueira <
>> rogerio.carrasque...@gmail.com> wrote:
>>
>>> Hey Steven!
>>>
>>> Thanks for this information, do you have tried it before? I would like
>>> to move from 1.4 to lastest, do you think that is it possible?
>>>
>>> Thanks
>>>
>>> Em quarta-feira, 7 de junho de 2023 às 11:52:35 UTC-3, Steven Mapes
>>> escreveu:
>>>
>>>> I'd suggest looking into using Adam Johnson's Django-Upgrade told -
>>>> https://github.com/adamchainz/django-upgrade it will help you move
>>>> between versions
>>>>
>>>> On Tuesday, 6 June 2023 at 15:24:36 UTC+1 Paul Haguet wrote:
>>>>
>>>>> There is a lot of function who can change.
>>>>>
>>>>> https://docs.djangoproject.com/en/4.2/releases/4.0/
>>>>>
>>>>> All the function declared as deprecated into Django 3 has been removed
>>>>> into Django 4. In the deprecated section of django 3 new functions names
>>>>> are systematically indicated. So just search the function under their old
>>>>> name and replace them with their new name. The 2 links below give the 
>>>>> list.
>>>>>
>>>>>
>>>>> https://docs.djangoproject.com/en/4.2/releases/3.0/#deprecated-features-3-0
>>>>>
>>>>> https://docs.djangoproject.com/en/4.2/releases/3.1/#deprecated-features-3-1
>>>>>
>>>>> Le samedi 3 juin 2023 à 10:10:31 UTC+2, Shams Ulhaq a écrit :
>>>>>
>>>>>> Just need to change url import
>>>>>>
>>>>>> from django.urls import include, re_path as url
>>>>>>
>>>>>>
>>>>>> On Sat, 3 Jun 2023, 12:32 David Nugent,  wrote:
>>>>>>
>>>>>>> nppe url is obsolete and removed in 4.x.
>>>>>>>
>>>>>>> You can use re_path, which is a kind of replacement but even then
>>>>>>> you will need to adjust the regex in many cases.
>>>>>>>
>>>>>>> The best approach is to understand what the url() is doing, and
>>>>>>> replicate the same using path(). Once you do, the conversions should be
>>>>>>> more or less straight-forward. Instead of regex you use labelled 
>>>>>>> patterns
>>>>>>> making for more comprehensible path lines. For complex regex expressions
>>>>>>> you may need to define custom matches - or "converters" - that enforce
>>>>>>> specific patterns allowing you to restrict input and improve matching. 
>>>>>>> This
>>>>>>> is one area that Django has improved really well over time.
>>>>>>>
>>>>>>> But, like I said, don't try to replace this file wholesale. Instead
>>>>>>> of converting it and doing error-fix-error-fix ad infinit

Re: how to convert to Django 3 or 4

['Steven Mapes' via Django users]

I've used it to go from Django 3 to 4 and to move a project from 1.11 to
2.2.

It doesn't do everything for you but it's a great start. I've personally
moved from 1.8 through to 4.2.2 but that was during their development
lifecycle. Moving up to 1.7 and then 1.7 to 1.8 and 1.8 to 1.11 and 1.11 to
2 will be the hardest parts but it'll get easier once you're on 1.11

On Thu, Jun 8, 2023, 19:58 Rogério Carrasqueira <
rogerio.carrasque...@gmail.com> wrote:

> Hey Steven!
>
> Thanks for this information, do you have tried it before? I would like to
> move from 1.4 to lastest, do you think that is it possible?
>
> Thanks
>
> Em quarta-feira, 7 de junho de 2023 às 11:52:35 UTC-3, Steven Mapes
> escreveu:
>
>> I'd suggest looking into using Adam Johnson's Django-Upgrade told -
>> https://github.com/adamchainz/django-upgrade it will help you move
>> between versions
>>
>> On Tuesday, 6 June 2023 at 15:24:36 UTC+1 Paul Haguet wrote:
>>
>>> There is a lot of function who can change.
>>>
>>> https://docs.djangoproject.com/en/4.2/releases/4.0/
>>>
>>> All the function declared as deprecated into Django 3 has been removed
>>> into Django 4. In the deprecated section of django 3 new functions names
>>> are systematically indicated. So just search the function under their old
>>> name and replace them with their new name. The 2 links below give the list.
>>>
>>>
>>> https://docs.djangoproject.com/en/4.2/releases/3.0/#deprecated-features-3-0
>>>
>>> https://docs.djangoproject.com/en/4.2/releases/3.1/#deprecated-features-3-1
>>>
>>> Le samedi 3 juin 2023 à 10:10:31 UTC+2, Shams Ulhaq a écrit :
>>>
 Just need to change url import

 from django.urls import include, re_path as url


 On Sat, 3 Jun 2023, 12:32 David Nugent,  wrote:

> nppe url is obsolete and removed in 4.x.
>
> You can use re_path, which is a kind of replacement but even then you
> will need to adjust the regex in many cases.
>
> The best approach is to understand what the url() is doing, and
> replicate the same using path(). Once you do, the conversions should be
> more or less straight-forward. Instead of regex you use labelled patterns
> making for more comprehensible path lines. For complex regex expressions
> you may need to define custom matches - or "converters" - that enforce
> specific patterns allowing you to restrict input and improve matching. 
> This
> is one area that Django has improved really well over time.
>
> But, like I said, don't try to replace this file wholesale. Instead of
> converting it and doing error-fix-error-fix ad infinitun, re-implement
> things as you enable parts of the app you have successfully ported. While
> re_path may be a fallback, try to re-implement as path() expressions and
> you'll be better in the long run.
>
>
> On Sat, Jun 3, 2023 at 11:59 AM Muhammad Juwaini Abdul Rahman <
> juw...@gmail.com> wrote:
>
>> I think Django 4 still have backward compatibility with `url`
>> although `path` is preferable.
>>
>> You can try to `runserver` in your local, upgrade your django version
>> in your virtualenv to version 4 and troubleshoot the error messages (if
>> any) one by one.
>>
>> On Sat, 3 Jun 2023 at 05:20, john fabiani 
>> wrote:
>>
>>> Hi everyone,
>>>
>>> I am tasked with updating/upgrading a very old Django web site - I
>>> believe it is 1.7.  I need convert and need what is required.
>>> Thanks in advance.
>>>
>>>
>>> I need to convert the following:
>>>
>>> from django.conf.urls import patterns, include, url
>>> from django.contrib import admin
>>> from django.conf import settings
>>> from django.conf.urls.static import static
>>>
>>> urlpatterns = patterns('',
>>> # Examples:
>>> url(r'reg4/$', 'register.views.reg4', name='reg4'),
>>> url(r'reg3/$', 'register.views.reg3', name='reg3'),
>>> url(r'reg2/$', 'register.views.reg2', name='reg2'),
>>> #url(r'reg1/$', 'register.views.reg1', name='reg1'),
>>> url(r'reg1/$', 'register.views.reg1', name='reg1'),
>>> #url(r'^$', 'register.views.home', name='home'),
>>> url(r'reg/$', 'register.views.home', name='home'),
>>> url(r'get_courts/(\d+)$', 'register.views.get_courts',
>>> name='get_courts'),
>>> url(r'get_courses/(\d+)$', 'register.views.get_courses',
>>> name='get_courses'),
>>> url(r'autoschedule/', 'register.views.autoschedule',
>>> name='autoschedule'),
>>> url(r'get_cities/(\d+)$', 'register.views.get_cities',
>>> name='get_cities'),
>>> url(r'get_classes/(\d+)$', 'register.views.get_classes',
>>> name='get_classes'),
>>> url(r'get_cities2/(\d+)/(\d+)/$', 'register.views.get_cities2',
>>> name='get_cities2'),
>>> url(r'get_classes2/(\d+)/(\d+)/$',
>>> 'register.views.get_classes2', 

Re: how to convert to Django 3 or 4

['Steven Mapes' via Django users]

I'd suggest looking into using Adam Johnson's Django-Upgrade told 
-https://github.com/adamchainz/django-upgrade it will help you move between 
versions

On Tuesday, 6 June 2023 at 15:24:36 UTC+1 Paul Haguet wrote:

> There is a lot of function who can change. 
>
> https://docs.djangoproject.com/en/4.2/releases/4.0/
>
> All the function declared as deprecated into Django 3 has been removed 
> into Django 4. In the deprecated section of django 3 new functions names 
> are systematically indicated. So just search the function under their old 
> name and replace them with their new name. The 2 links below give the list.
>
> https://docs.djangoproject.com/en/4.2/releases/3.0/#deprecated-features-3-0
> https://docs.djangoproject.com/en/4.2/releases/3.1/#deprecated-features-3-1
>
> Le samedi 3 juin 2023 à 10:10:31 UTC+2, Shams Ulhaq a écrit :
>
>> Just need to change url import 
>>
>> from django.urls import include, re_path as url
>>
>>
>> On Sat, 3 Jun 2023, 12:32 David Nugent,  wrote:
>>
>>> nppe url is obsolete and removed in 4.x.
>>>
>>> You can use re_path, which is a kind of replacement but even then you 
>>> will need to adjust the regex in many cases.
>>>
>>> The best approach is to understand what the url() is doing, and 
>>> replicate the same using path(). Once you do, the conversions should be 
>>> more or less straight-forward. Instead of regex you use labelled patterns 
>>> making for more comprehensible path lines. For complex regex expressions 
>>> you may need to define custom matches - or "converters" - that enforce 
>>> specific patterns allowing you to restrict input and improve matching. This 
>>> is one area that Django has improved really well over time.
>>>
>>> But, like I said, don't try to replace this file wholesale. Instead of 
>>> converting it and doing error-fix-error-fix ad infinitun, re-implement 
>>> things as you enable parts of the app you have successfully ported. While 
>>> re_path may be a fallback, try to re-implement as path() expressions and 
>>> you'll be better in the long run.
>>>
>>>
>>> On Sat, Jun 3, 2023 at 11:59 AM Muhammad Juwaini Abdul Rahman <
>>> juw...@gmail.com> wrote:
>>>
 I think Django 4 still have backward compatibility with `url` 
 although `path` is preferable.

 You can try to `runserver` in your local, upgrade your django version 
 in your virtualenv to version 4 and troubleshoot the error messages (if 
 any) one by one.

 On Sat, 3 Jun 2023 at 05:20, john fabiani  wrote:

> Hi everyone,
>
> I am tasked with updating/upgrading a very old Django web site - I 
> believe it is 1.7.  I need convert and need what is required.
> Thanks in advance.
>
>
> I need to convert the following:
>
> from django.conf.urls import patterns, include, url
> from django.contrib import admin
> from django.conf import settings
> from django.conf.urls.static import static
>
> urlpatterns = patterns('',
> # Examples:
> url(r'reg4/$', 'register.views.reg4', name='reg4'),
> url(r'reg3/$', 'register.views.reg3', name='reg3'),
> url(r'reg2/$', 'register.views.reg2', name='reg2'),
> #url(r'reg1/$', 'register.views.reg1', name='reg1'),
> url(r'reg1/$', 'register.views.reg1', name='reg1'),
> #url(r'^$', 'register.views.home', name='home'),
> url(r'reg/$', 'register.views.home', name='home'),
> url(r'get_courts/(\d+)$', 'register.views.get_courts', 
> name='get_courts'),
> url(r'get_courses/(\d+)$', 'register.views.get_courses', 
> name='get_courses'),
> url(r'autoschedule/', 'register.views.autoschedule', 
> name='autoschedule'),
> url(r'get_cities/(\d+)$', 'register.views.get_cities', 
> name='get_cities'),
> url(r'get_classes/(\d+)$', 'register.views.get_classes', 
> name='get_classes'),
> url(r'get_cities2/(\d+)/(\d+)/$', 'register.views.get_cities2', 
> name='get_cities2'),
> url(r'get_classes2/(\d+)/(\d+)/$', 'register.views.get_classes2', 
> name='get_classes2'),
> url(r'rejected/$', 'register.views.rejected', name='rejected'),
> url(r'finished/$', 'register.views.finished', name='finished'),
> 
> ##url(r'^$', 'profiles.views.home', name='home'),
> #url(r'^contact/$', 'register.views.home', name='contact'),
> #url(r'^about/$', 'register.views.about', name='about'),
> #url(r'^profile/$', 'register.views.user_profile', name='profile'),
> #url(r'^checkout/$', 'checkout.views.checkout', 
> name='checkout'),
> # url(r'^blog/', include('blog.urls')),
>
> url(r'^admin/', include(admin.site.urls)),
> ) + static(settings.STATIC_URL, document_root = settings.STATIC_ROOT)
>
> What is required?
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "Django users" group.
> To unsubscribe from 

Re: Django Froala Editor

['Steven Mapes' via Django users]

Sorry hit send too soon. An alternative is to update your settings.py entry 
for FROALA_STORAGE_BACKEND to point to a different backend as per their 
docs https://github.com/froala/django-froala-editor#other-settings

On Friday, 3 February 2023 at 14:30:12 UTC Steven Mapes wrote:

> Easiest way will be to overload their default upload view.
>
> If you look in the urls.py for the package it has two entries
>
>
> *path('image_upload/', views.image_upload, 
> name='froala_editor_image_upload'),path('file_upload/', views.file_upload, 
> name='froala_editor_file_upload'),*
>
> Take a look at those view here 
> https://github.com/froala/django-froala-editor/blob/master/froala_editor/views.py
>
> Then create your own views doing what you want but serve them from the URL 
> path that these would be on by default so that they are called instead.
>
> On Friday, 3 February 2023 at 12:00:32 UTC akino...@gmail.com wrote:
>
>> Please I need help on how to change the upload path of django froala 
>> editor. Possiby to Cloudinary 
>> Please I need help 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/39b39288-711b-464a-9f13-e9d3173a62a8n%40googlegroups.com.

Re: Django Froala Editor

['Steven Mapes' via Django users]

Easiest way will be to overload their default upload view.

If you look in the urls.py for the package it has two entries


*path('image_upload/', views.image_upload, 
name='froala_editor_image_upload'),path('file_upload/', views.file_upload, 
name='froala_editor_file_upload'),*

Take a look at those view 
here 
https://github.com/froala/django-froala-editor/blob/master/froala_editor/views.py

Then create your own views doing what you want but serve them from the URL 
path that these would be on by default so that they are called instead.

On Friday, 3 February 2023 at 12:00:32 UTC akino...@gmail.com wrote:

> Please I need help on how to change the upload path of django froala 
> editor. Possiby to Cloudinary 
> Please I need help 

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/f2a9d21c-1ac6-4bbd-8eb3-c4061ea148f4n%40googlegroups.com.

Re: Django microservice authentication problem.

['Steven Mapes' via Django users]

Are you trying to authenticate via Django Rest FrameWork API or via the 
standard Django authentication system?  It shouldn't really matter which it 
is as both can be scaled horizontally and you'll have no issue with 
authenticating so in order for us to help we'd need to understand what you 
are doing better.

For example are you trying to share the database across multiple domains? 
Are you simply placing multiple servers behind a load balancer on the same 
domain?

On Saturday, 28 January 2023 at 06:53:12 UTC mdanar...@gmail.com wrote:

> How to communicate and authenticate with multiple Django servers. Is it 
> possible?
>
> If possible you can help me, I am trying more than 15 days in this section 
> but not getting any solution.
>
> Please share with me any requirements like books, videos, blogs, or code 
> examples.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/16326b9e-0656-45b4-b975-faf9b676a559n%40googlegroups.com.

Re: Card-Payment Integration.

['Steven Mapes' via Django users]

There's several that you'll find integration projects for on github, 
personally I wrote my own lib to integrate Stripe and Paypal and much 
prefer stripe over paypal. it's a cleaner integration, faster flow for the 
user, lower fees, allows refunds for payments of any age whilst the card is 
valid and, for my clients, the money is paid out. Had lots of bad 
experience with Paypal withholding money for clients for over a year 
because they don't understand their business model and stopping refunds 
after 3 months even if the business allows them for longer

On Tuesday, 3 January 2023 at 13:37:39 UTC satyajit...@gmail.com wrote:

> You can try Paypal or Braintree payment gateway. Both work perfectly.
>
>
> Regards,
> Satyajit
>
> On Tue, Jan 3, 2023 at 9:56 AM Mike Dewhirst  
> wrote:
>
>> On 3/01/2023 3:12 pm, Harshwardhan Waghela wrote:
>>
>> Other Then Stripe ?  
>>
>>
>> Speak to your favourite bank and see what they offer. That's what I did 
>> before going to Stripe. 
>>
>> Otherwise google for local gateway providers.
>>
>>
>> On Monday, 2 January 2023 at 18:05:34 UTC+5:30 Mike Dewhirst wrote:
>>
>>> I use Stripe. It works well.
>>>
>>> Mike
>>>
>>>
>>>
>>> -- 
>>> (Unsigned mail from my phone) 
>>>
>>>
>>>
>>>  Original message 
>>> From: Harshwardhan Waghela  
>>> Date: 2/1/23 22:40 (GMT+10:00) 
>>> To: Django users  
>>> Subject: Card-Payment Integration. 
>>>
>>> Can Anyone Can Suggest me of Card-Payment Integration(means Visa, 
>>> Master-Card...etc)  with Documentation.
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to django-users...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/django-users/a6d08f33-f1eb-4d1a-8247-c17236859d59n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/a37322f4-2354-46ea-8618-6626f7dcb812n%40googlegroups.com
>>  
>> 
>> .
>>
>>
>>
>> -- 
>> Signed email is an absolute defence against phishing. This email has
>> been signed with my private key. If you import my public key you can
>> automatically decrypt my signature and be sure it came from me. Just
>> ask and I'll send it to you. Your email software can handle signing.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/9cb82857-9a09-4da3-1ca6-792a39271d7e%40dewhirst.com.au
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/9d763ba9-37fc-4839-8ade-01906772b8f4n%40googlegroups.com.

Re: Looking for available support to start a School Management Application

['Steven Mapes' via Django users]

I'd be very reluctant to use existing OS projects for such a project unless 
they have proven security and a strong policy in place as you're talking 
about handling sensitive data.

You should also double check with the school what license requirements they 
have as many will not allow 3rd party packages to be included for security 
or IP reasons.



On Monday, 7 November 2022 at 14:09:30 UTC julika...@gmail.com wrote:

> You have to do it yourself
> Not cloning an existing project on GitHub
> This will help you deburg the code yourself 
>
> On Mon, Nov 7, 2022, 5:03 PM Milson Munakami  wrote:
>
>> You can give it a try, my open sourced side project: 
>> https://github.com/Milstein/Student_Management_System
>>
>> On Mon, Nov 7, 2022 at 4:48 AM Eric Francis  wrote:
>>
>>> Many thanks for all your feedback.
>>> I will share details on what has been requested and the level of what I 
>>> have done so far.
>>> Thank you
>>>
>>> Eric
>>>
>>> On Mon, 7 Nov 2022, 12:33 kateregga julius,  wrote:
>>>
 Before starting on the system.
 Do information gathering,
 Design your database schema. 
  (Visual paradigm)
 Then set your development environment 

 On Mon, Nov 7, 2022, 11:44 AM Adekola Aderonmu  
 wrote:

> I am also interested  in collaborating with you. 
>
> On Mon, 7 Nov 2022, 06:37 DJANGO DEVELOPER,  
> wrote:
>
>> Are you looking for a paid support?
>>
>> On Mon, 7 Nov 2022, 9:41 am ritik sahoo,  wrote:
>>
>>> I have 
>>>
>>> On Mon, 7 Nov, 2022, 5:34 am Makrand,  wrote:
>>>
 I have developed School management system. I am interested to 
 complete support.

 On Mon, Nov 7, 2022, 4:27 AM Ahmed omar miladi <
 ahmedom...@gmail.com> wrote:

> hello frncseric i'm ahmed omar miladi i'm full stack developer and 
> django specialist i build a platform with name is allcarta check 
> https://www.allcarta.com and i can help you to build a 
> school management system
>
> On Sun, 6 Nov 2022 at 23:05, nef  wrote:
>
>> Hi everyone,
>> I am beginer in Django, not much experience.
>> I have been task to develop an application for school management 
>> (Admission, Registration,  Attendance, Report marks, and more 
>> functions).
>> I am wondering if there is an existing open smilare app or 
>> something which can be use as baseline to start or guide me with 
>> best 
>> practices.
>> Thank you
>> Eric
>>
>> -- 
>> You received this message because you are subscribed to the 
>> Google Groups "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to django-users...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/176ec5a0-2e00-4f53-b5c3-1bfc72f3aa94n%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, 
> send an email to django-users...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/CAE3Dc2PkKJUF19fSykG%2BAmYByW6MY49UW%3DHSiKEL%2BPnZ6CHrvA%40mail.gmail.com
>  
> 
> .
>
 -- 
 You received this message because you are subscribed to the Google 
 Groups "Django users" group.
 To unsubscribe from this group and stop receiving emails from it, 
 send an email to django-users...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/django-users/CAA_ekM%2BRQKYixBpZnZzYaN9cE9ete_PpPX%2BVJEj3e%2B%2BK2jktbQ%40mail.gmail.com
  
 
 .

>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Django users" group.
>>> To unsubscribe from this group and stop receiving emails from it, 
>>> send an email to django-users...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/django-users/CAJwehCvV8YkQXf5y5AM_OGTH0vmv_f_kuHyTq7K0p_HyKG3-Sg%40mail.gmail.com
>>>  
>>> 

Re: Using django 4.1 code in django 3.2

['Steven Mapes' via Django users]

It'll depend on whether your code is 3.2 compatible or not so you'd need to 
test it and check dependencies first

On Thursday, 3 November 2022 at 09:28:40 UTC Kasper Laudrup wrote:

> On 03/11/2022 10.18, Lakshyaraj Dash wrote:
> > Is there any problem if I deploy my django app written with django 4.1 
> > in django 3.2 on render ?
>
> Yes.
>
> Kind regards,
> Kasper Laudrup
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/cb156148-ba0d-4460-bb54-cacc4cba9660n%40googlegroups.com.

Re: Looking for a Django firm

['Steven Mapes' via Django users]

I would be interesting in learning more Mike as would a one of my other 
business partners, both run companies UK based. https://mapestech.co.uk 
and https://www.springbourne-tech.com/

On Tuesday, 13 September 2022 at 01:02:09 UTC+1 Mike Dewhirst wrote:

> Hi all - I'm looking for a Django outfit with an interest in chemistry 
> or customers in the chemical industry in Australia.
>
> Possible opportunity.
>
> Best to respond off list and there will be an NDA.
>
> Cheers
>
> Mike
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/39c21d50-4dd8-4ce0-adfb-6f2b7f816c02n%40googlegroups.com.

Re: upgrading from 1.11 and ran into builtin permission clash

['Steven Mapes' via Django users]

What I'd advise is to upgrade to point just before it breaks, then update 
the permission to use a different name, then upgraded to 2.2 avoiding the 
name clash. Once upgraded then edit the permission to grant the permission 
to the users who need that permission based on your now renamed custom 
permission. Then remove your custom permission.

I'd do it this way so that you don't loose data on which users had that 
permission in the first place.  Or rename the permission at the start then 
upgrade.

For those saying "why not upgrade to 4" there are many good reasons why you 
may not/ can not, use Django 4 at the moment such as reliance on 
unsupported 3rd party libs or, more commonly, regressions and lack of LTS.  
It's quite common for companies/projects that need stability to only 
upgrade from LTS version to LTS version as they can't risk the regressions 
that often happen in between

On Sunday, 3 July 2022 at 14:16:36 UTC+1 jefrisimo...@gmail.com wrote:

> Deal
>
>
> Pada tanggal Min, 3 Jul 2022 03.48, Sheila Miguez  
> menulis:
>
>> I could try that.
>>
>> So far I've made a toy project to reproduce the problem and made a 
>> migration in 1.11 to remove the permission. When I started it up in 2.2 it 
>> suddenly said I had unapplied migrations in admin and auth.
>>
>> I don't know if renaming would have the same effect. I'll try it.
>>
>> On Friday, July 1, 2022 at 11:35:02 AM UTC-5 Jason wrote:
>>
>>> Joel Goldstick, would definitely not recommend doing an all in one 
>>> update.  That'd be like going from windows XP to 10 in one go.  For 
>>> personal projects, you could do it, but would side-eye any professional who 
>>> suggested doing this with a company or workplace project.
>>>
>>> https://docs.djangoproject.com/en/4.0/releases/2.1/#model-view-permission 
>>> is 
>>> liekly the permission being hit.  OP, would it be possible for you to 
>>> rename the original permission name in a migration in 1.11, and then move 
>>> forward with the migration?
>>>
>>>
>>> On Friday, July 1, 2022 at 9:35:31 AM UTC-4 mma...@gmail.com wrote:
>>>
 > What do I do about this? Clearly I should remove the permission I 
 created. How do I deal with the migration? Should I remove the permission 
 while I run the app as Django 1.11 before moving on to a 2.2 environment? 

 You could rename the current view_inventorychangelog record with a data 
 migration to avoid the constraint, upgrade to 2.2, and then move any 
 references to the old DB record to the new using a data migration.

 > Sorry, I can't answer your question. But, I am wondering why you are 
 > upgrading to a very out of date version of Django that is no longer 
 > supported. I think 3.2 is the oldest supported version. Why not 
 > upgrade to 4? 

 The options for uplifting severely out of date projects are to either 
 step-by-step migrate through older versions, or rewrite in the target 
 version.

 Cheers,
 Michael Manfre

 -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/cdfce75a-6bb1-4d1b-81a5-a03785cdddb4n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ef92d745-6cb1-41c2-9285-f4c0722759a3n%40googlegroups.com.

Re: Looking for experienced Django backend engineer

['Steven Mapes' via Django users]

I'm always looking for new clients, over 2 decades development experience, 
server admin experience, DBA etc See https://www.mapestech.co.uk/ for more

On Monday, 4 July 2022 at 04:11:26 UTC+1 anderso...@gmail.com wrote:

> Just forward to my teammate. 
> Good luck 
>
> On Sun, Jul 3, 2022 at 2:04 PM Mohammad Foysal  wrote:
>
>>
>> I have been working with python for the last two years. so I feel that I 
>> have some transferable skills to the position you are looking for. As a web 
>> application developer I have professional experience in various concepts of 
>> design and development.
>>
>> Please find enclosed my CV if you have any questions about my skills and 
>> experiences.
>>
>> Thank you for your time and consideration and I look forward to hearing 
>> from you soon.
>>
>>
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Django users" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/django-users/veFA7lPluGg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> django-users...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/529F41A5-EF89-437E-9DEF-5A1F6909811C%40gmail.com
>>  
>> 
>> .
>
>
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Django users" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/django-users/veFA7lPluGg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> django-users...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/529F41A5-EF89-437E-9DEF-5A1F6909811C%40gmail.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/e9b1b040-0a5e-4167-a947-25169bd26661n%40googlegroups.com.

Re: django html error

['Steven Mapes' via Django users]

If you check the output of runserver can you see a HTTP200 response? If so 
then the best starting place is to look into your projects base 
.urls.py and match up the URL you are requesting to the view 
being used. Once you have that what is happening next will depend on 
whether you are using functional views of class-based views.  If you are 
using an IDE with debugging such as PyCharm then I'd suggest adding a 
breakpoint walking through the code to make sure it is using  the view you 
expect

On Monday, 4 April 2022 at 01:40:08 UTC+1 rakeshsh...@gmail.com wrote:

> Will you send me some project codes pics so that i can help you.
>
> On Sat, 2 Apr, 2022, 8:34 pm 5021-Chandra Prakash.S,  
> wrote:
>
>> i am new to django, there is no error in my project but my html page is 
>> not loading ,its just appearing white blank screen when i run the server.I 
>> had checked settings.py file and edited the templates setting but then too 
>> my html file isn't loading.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to django-users...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/e2efbfba-b612-48d8-9012-e277cb21d7e9n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/23574240-b320-4e55-a668-a2f2f95ca4abn%40googlegroups.com.

Re: Django 1.5 app had subclasses without tables without proxy and now 1.6 won't sync with proxy

['Steven Mapes' via Django users]

Migrations came in in 1.7 the docs for 1.8 show the following


*Prior to version 1.7, Django only supported adding new models to the 
database; it was not possible to alter or remove existing models via 
the syncdb command (the predecessor to migrate 
).**Third-party
 
tools, most notably South , provided support 
for these additional types of change, but it was considered important 
enough that support was brought into core Django.*
I'd like to wish you good luck in making the move. I remember going from 
1.8 to 1.11 was often a pain and 1.11 to 2 a little less. Personally 
depending on the size of the project I'd be tempted to dump the data 
against whichever data it is and start a whole new project from scratch 
then import the data in at the end and then use django dumps-data but I 
feel your pain
On Monday, 4 April 2022 at 16:24:10 UTC+1 Antonis Christofides wrote:

> This looks strange, although I'm not familiar with exactly this particular 
> use case. I'm assuming you are referring to multi-table inheritance. Are 
> you certain Django 1.5 wasn't creating these tables? Was it using 
> migrations or South maybe? (Obviously I don't remember when Django started 
> supporting migrations.) When you say it tries to query these tables, when 
> does it attempt to do so? Could you post an example of a subclasss, 
> preferably with its base class?
>
>
> On 04/04/2022 09.09, John Abraham wrote:
>
> Hello. We're migrating someone else's app that was at Django 1.5.12 and 
> we're trying to bring it more up-to-date, step-by-step, starting with 
> Django 1.6.11. 
>
> There's an odd thing. There were a bunch of subclasses of a Model class, 
> that didn't have any database fields. Django wasn't creating nor using 
> tables for them at 1.5.12. But, Django 1.6.11 keeps trying to query these 
> non-existent tables for these subclasses, expecting them to have a single 
> field which would just be the pointer to their superclass.
>
> It seems the proper way to tell Django not to use tables for a class is to 
> set:
>
> class Meta:
> proxy = True
>
> But if we put this in, then when we run syncdb it strangly tries to query 
> the base classes before any tables are created at all in the database.  
>
> Any old-timers run into anything like this? Did Django 1.5 not need the 
> proxy = True in the meta to avoid creating tables for subclasses of Models 
> that didn't add any fields?
>
> They are using InheritanceManager from django_model_utils. 
>
> Thanks for any help! Banging our heads against the wall on this one for 
> quite a while now...
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to django-users...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/45eec62d-a27c-4b5e-b8ff-6fc2981efa17n%40googlegroups.com
>  
> 
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2fe87247-13ba-41d5-a38e-6915de6822b3n%40googlegroups.com.