Hi from Gitcoin.

We are seeing an issue at https://gitcoin.co/wiki/get_started/get-started-grant when we click edit and the server completely times out.

Is there any known issue that could be causing this. Do u have any tips of how to profile this call on our install?

When I upload an image in an wiki page it's getting up loaded to the server to in the location:

media/wiki/images/9/3ebe4e2f840a4437b3de1d35c1b06ac2/P9260018.JPG

I can point my browser at that file directly using it as a URL and the image gets displayed in my browser. So the image is there and is being served by the web server (Nginx). However when the image is embedded in a wiki page with "[image:1]" I get "image not found" being displayed instead of the image.

I've looked at nginx logs I'm getting two error lines:

2016/10/04 17:56:35 [error] 1236#0: *1 directory index of ".../media/wiki/images/9/3ebe4e2f840a4437b3de1d35c1b06ac2/" is forbidden, request: "GET /media/wiki/images/9/3ebe4e2f840a4437b3de1d35c1b06ac2/ HTTP/1.1",

2016/10/04 18:00:18 [error] 1236#0: *11 open() ".../media/wiki/images/9/P9260018.JPG" failed (2: No such file or directory), request: "GET /media/wiki/images/9/P9260018.JPG HTTP/1.1",

So it appears that the directory don't have permission to be indexed but on my server there is permission in the linux file system. Since django-wiki created this directory structure on the server I'd assume that it would set up the permissions required.

Todo list for complete #1199:

• [x] Create pyproject file
  • [x] Drop setup.py|cfg
• [x] Add new environments for development lifecycle
  • [x] Test environment
  • [x] Develop environment
  • [x] Transifex environment
  • [x] Documentation environment
• [x] Migrate Makefile commands to hatch commands
  • [x] Test commands
  • [x] Develop commands
  • [x] Transifex commands
  • [x] Documentation commands
• [x] Add documentation for development/test/release commands
• [x] Test sdist and wheel distribution

Updated after a complete port (Nov 21, 2022):

• [x] Drop tox.ini configuration and use hatch test matrix
• [x] Update circleci configuration in order to use pyproject file
• [x] Migrate pytest config to toml file
• [x] Docs command set conf.py path
• [x] Update or drop Manifest.in file

I'm using GAE which forces me to use blobstore for file uploading.

Therefore, I am in the process of hacking your code to learn to create my own plugin.

I am planning to use the original image plugin as my starting point.

I it'll help me a lot if you give me a heads up for things that I should look into.

If you think my situation is general enough I'd be glad to request a pull when I'm done.

I will try to explain the best as I can what I think is a bug but, given my relative knowledge of django could be some misconfiguration. Also, it could be more of a conflict between django wiki and S3 as storage.

The use case is: having a production cookiecutter django, with S3 configured, and django wiki as application. In fact locally this doesn't happen so I had to bring every AWS configuration locally to make it work.

When you delete an image, you get prompted if you want to delete the image. After that the method fires to delete the image. The problem is that ImageField using S3 storage class needs to use the "name" field instead of path because path isn't implemented in the storage class.

def on_image_revision_delete(instance, *args, **kwargs):
    if not instance.image:
        return
    # Remove image file
    path = instance.image.path.split("/")[:-1] #path returns not implemented, while .name works.
    instance.image.delete(save=False)

diango.core.files.storage.py

def path(self, name):
        """
        Return a local filesystem path where the file can be retrieved using
        Python's built-in open() function. Storage systems that can't be
        accessed using open() should *not* implement this method.
        """
        raise NotImplementedError("This backend doesn't support absolute paths.")

I realize that my explanation is faulty and missing some basic knowledge, sorry for that, I'm currently deepening my django skills so maybe there is something basic that I might be missing. I hope this helps figuring out a way to allow using S3 as a storage.

It would be much appreciated to know if this is an issue or if I just missed something. I will post to stack overflow for help anyway but if this is an error I'd like to help fixing it.

I'd like to have the wiki as the root of my site, but set aside a section /blog that is not managed by django-wiki. This is easily accomplished in urls.py, but there's nothing to stop someone entering /blog as the slug in a new article. I can think of 2 different solutions:

1. Blacklist certain slugs/urls
2. Only allow admins to create root level articles

Is this possible at the moment?

I'm having problems with getting images to show up.

Pages show "Image not found" but I can still browse images, they upload successfully, they just don't show.

I can see in my media folder that images are going into there (/media/wiki/images/1/043d6f8db89b72f0a9c39a4030363e78/picture.png).

Have gone through the process of setting up django-wiki in a project several times and have come to this same problem. Help is greatly appreciated, I really like django-wiki.

STATIC_URL, MEDIA_URL and STATIC_ROOT, MEDIA_ROOT are all set like so:

MEDIA_ROOT = os.path.join(PROJECT_PATH, "media") MEDIA_URL = '/media/' STATIC_ROOT = os.path.join(PROJECT_PATH, "static") STATIC_URL = '/static/'

From https://simplemde.com/ and https://github.com/onepill/django-simplemde

install django-simplemde

pip install django-simplemde

2 add 'simplemde' to INSTALLED_APPS.

INSTALLED_APPS = (
    # ...
   ` 'simplemde',`
    # ...
)

In wiki forms.py

Add from wiki.simplemde.widgets import SimpleMDEEditor

In class

"CreateRootForm", "EditForm", "CreateForm"

Replace:

widget=getEditor().get_widget()`   with  `widget=SimpleMDEEditor() 

Do the same in admin.py

5. optional 'recommended' You could set SimpleMDE options in settings.py like this:

SIMPLEMDE_OPTIONS = {
    'hideIcons':["guide", "heading"],
    'showIcons':["heading-2"],
    'promptURLs': True,
    'spellChecker': False,
    'placeholder': 'haha',
    'status': False,
    'autosave': {
        'enabled': True
    }
}

Hey all,

Great work on the wiki - it was quick and easy to install and looks great out of the box. I've got a question on your GPLv3 license - does including the wiki on a commercial public facing Django site require the entire site to be open sourced? Or would it comply with the license if I only made the wiki portion of the site available and the rest remained under copyright?

django-wiki: needs django.core.context_processors.request in TEMPLATE_CONTEXT_PROCESSORS') django.core.exceptions.ImproperlyConfigured: django-wiki: needs django.core.context_processors.request in TEMPLATE_CONTEXT_PROCESSORS

It seems django.core.context_processors has been depreciated in 1.8 into django.template.context_processors.

Work towards closing off https://github.com/django-wiki/django-wiki/issues/518

There are probably some tiny things i missed however this PR should cover most things (I used the testproject to make sure that most things have remain unchanged). The biggest difference is probably font size and spacings, which can be tweaked. I don't think it looks quite as polished as the current bootstrap 3 version, but it's not far off in my opinion.

• Select2 is used in favour of typeahead, since typeahead appears to be abandoned and doesn't play well with bootstrap4.
• jQuery-ui has been removed (also a bit of a dead project). This means the resizing of modals has been removed, but I think I've made that OK with some dynamic resizing according to window size.
• Font-awesome was updated to latest, since bootstrap4 uses scss and I had to make changes here for that anyway
• jQuery updated to latest

Respectful of read permissions, we should add preview cards for Fediverse, Twitter, Facebook, LinkedIn etc.

The default image path could perhaps be read from a setting.

I'm reporting a bug in search page.

I use japanese in django-wiki, but I found that content overview in search page is not work correctly especially in case using html tags in the content.

I realized that get_content_snippet() in wiki-tags.py is optimized only for the language using space between words, but Japanese don't use space between words.

I would like to propose the following in spite of current get_content_snippet()

@register.filter
def search_result_format(content, keyword, max_letters=300):

    content = striptags(content)
    content =re.sub(r'\r\n', ' ', content)
    content =re.sub(r'\n', ' ', content)
    keyword=re.escape(keyword)

    result=re.search(keyword, content, re.IGNORECASE)

    startposition=result.start()-int(max_letters/2)
    if startposition<0: startposition=0

    endposition=startposition+max_letters
    if endposition>len(content): endposition=len(content)

    result_content=content[startposition:endposition]

    if startposition>0:        
        #for the languages using space between words
        spase_position=result_content.find(" ")
        if spase_position >=0 and spase_position < 15: 
            result_content=result_content[spase_position:]

        result_content="...."+result_content

    if endposition<len(content):
        #for the languages using space between words
        spase_position=result_content.rfind(" ")
        if spase_position >=0 and len(result_content)-spase_position < 15: 
            result_content=result_content[:spase_position]

        result_content=result_content+"...."

    #html markup
    result_content=re.sub(r'('+keyword+')',r'<strong style="background:#ddd">\1</strong>',result_content ,flags=re.IGNORECASE)
    
    return result_content

The default of django-wiki should be to depend on pymdown-extensions and have out-of-the-box CSS support for a set of plugins.

https://facelessuser.github.io/pymdown-extensions/

Hello,

I recently upgraded to wiki==0.7.6 and for some reason I can't add any new page, because I get the following error

This slug conflicts with an existing URL.

although there is definitely no conflicting slug.

I do do some magic on the wiki urls to put them behind a login wall (see here). That said, this was not an issue with the previous versions of wiki.

Any ideas what the problem could be? Thanks!

I started to make test for models.baseplugins.py but I came across a problem

def test_reusable_plugins_related(self):
    a1 = Article.objects.create()
    a2 = Article.objects.create()

    p = ReusablePlugin.objects.create(article=a1)
    pk = p.pk
    p.articles.add(a2)
    p.save()

    self.assertEqual(a1, p.article)
    self.assertNotIn(a1, p.articles.all())

    p.article = None
    p.save() # <---- Raise a RelatedObjectDoesNotExist exception

    self.assertIsEqual(p.article, a2)

    a2.delete()
    with self.assertRaises(ReusablePlugin.DoesNotExist):
        ReusablePlugin.objects.get(pk=pk)

I feel like the intent of the presave signal isn't to raise an exception when instance.article is None.

@disable_signal_for_loaddata
def on_reusable_plugin_pre_save(**kwargs):
    # Automatically make the original article the first one in the added
    # set
    instance = kwargs["instance"]
    if not instance.article: # <---- Raise a RelatedObjectDoesNotExist exception
        articles = instance.articles.all()
        if articles.exists():
            instance.article = articles[0]

My guess is the following part in ReusablePlugin class didn't do anything or not anymore.

# The article on which the plugin was originally created.
# Used to apply permissions.
ArticlePlugin.article.on_delete = models.SET_NULL
ArticlePlugin.article.verbose_name = _("original article")
ArticlePlugin.article.help_text = _("Permissions are inherited from this article")
ArticlePlugin.article.null = True
ArticlePlugin.article.blank = True

According to the django documentation you cannot modified inherited fields without a proper abstract class, so the ReusablePlugin.article cannot be different than ArticlePlugin.article

I dont know how much of a hindrance it is for attachment plugin but we should either :

• remove the part of the code that threat ReusablePlugin.article as if it has null==blank==True
• make ArticlePlugin class abstract (with database change)
• remove the inheritance of ReusablePlugin from ArticlePlugin (with database change)

keep in mind that it also mean that on_delete==models.CASCADE and if we keep the current code the feature "the attachment isnt deleted when the main Article is deleted" didnt work as intended i assume.

It would be nice if the documentation in some way mentioned how to have a Wiki in different languages, for instance what happens with /en/wiki and /fr/wiki supposing it's available in English and French:

• How to using i18n_patterns, maybe this should be a real code snippet example in the main installation instructions since it's so commonly needed
• How to host content in different languages (hint: it's not really supported but easy to make a solution for it)
• How to make a language switcher (perhaps just link to a solution)