Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter temp5

    (@temp5)

    Oh, sorry, I read over the fact that you use v2.

    I really can’t say much about your suggestion – maybe you are on the right track, but maybe you found a complete other problem.

    In my opinion the best bet to solve this “forever loading”-issue is to check the process where the parameters are extracted from the request uri.

    Best regards,
    temp5

    Thread Starter temp5

    (@temp5)

    I marked this thread as “resolved” because the workaround I posted before your post did the trick for me.
    The main problem with this issue is, that it only occurs to a bunch of people and under special circumstances, that, I think, the devs don’t know – because otherwise they would have fixed it already.

    Have you tried my workaround?

    Thread Starter temp5

    (@temp5)

    Hello pearl-grey,

    as I said: the fix is really quick and dirty and I don’t know if it will of any assistance for you, but of course I will try to help you (remember: I did this in version 1.10.11):
    Add the following:

    if (strpos($_SERVER['REQUEST_URI'], "request_type=json") !== false)
                            $type = "json";

    after line 918 (“$type = $this->request->get( 'request_type' );“) in file
    wp-content/plugins/all-in-one-event-calendar/app/controller/class-ai1ec-app-controller.php
    and after line 188 (“$type = $request->get( 'request_type' );“) in file wp-content/plugins/all-in-one-event-calendar/app/controller/class-ai1ec-calendar-controller.php .
    This really isn’t a neat solution, but it does the trick for me and hopefully for you.

    If you have any questions feel free to ask!

    Best regards,
    temp5

    Thread Starter temp5

    (@temp5)

    Of course you can! But I really don’t know if my solution will be of any assistance for them, because it really is a quick and dirty fix and was done in the old 1.10.11 and it seems that there are many other reasons that can lead to this behavior.

    Best regards,
    temp5

    Thread Starter temp5

    (@temp5)

    Ok, it seems the “Ai1ec_Abstract_Query”-class that manages the request uri had some issues extracting the request_type and so the type was always set to “standard”, which means: html-rendering.
    So I wrote a workaround that checks the request uri for “request_type=json” and sets the type corresponding to the result.
    Maybe not the nicest solution, but everything seems to work now!

    Best regards,
    temp5

Viewing 5 replies - 1 through 5 (of 5 total)