arvgta

Forum Replies Created

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

  • Error seems to persist: https://4nf.org/
    (counting twice)

    Same thing here: https://4nf.org/
    Otherwise a great plugin!

    Thread Starter arvgta

    (@arvgta)

    Here some additional information, what I’ve done in the child-theme:

    – Dropped in a favicon.ico
    – Supplied a style.css (see below)
    – Supplied a functions.php (see below)
    – Supplied my custom inclusion of jQuery (see below)

    style.css:

    /**
 * Theme Name:     4nfext
 * Description:    Child theme for realising 4nf.org extensions
 * Author:         Arvind Gupta
 * Author URI:     https://github.com/arvgta
 * Template:       twentyfifteen
 * Version:        0.1.0
 */

@import url("../twentyfifteen/style.css");

#sidebar {background-color: darkorange; opacity:0.8;}
.page {background-color: aliceblue;}
.jqhover {background-color: orange;}

    functions.php:

    <?php
add_action('wp_enqueue_scripts', 'no_more_jquery');
function no_more_jquery(){
    wp_deregister_script( 'jquery' );
    wp_deregister_script( 'jquery-ui-core' );
}
?>

    Override with my custom jQuery in the head:

    <script src='https://code.jquery.com/jquery-3.0.0-alpha1.js' type="text/javascript"></script>
<script src="https://ajax.googleapis.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js"></script>

    I have tested using the theme’s jQuery versions as well – has nothing to do with the jQuery version…

    Any ideas?

    Thread Starter arvgta

    (@arvgta)

    Worked around it, by altering quotes in a comment, that were causing the problem.

    But I presume it is the above bug, that causes these symptoms…

    Thread Starter arvgta

    (@arvgta)

    Thanks for your reply – much appreciated!

    Yes, permalinks are enabled.

    To be more precise, my first attempt was to rename the 404.php in the parent’s theme, assuming that it wouldn’t be fetched anymore.
    I have no idea, whether it was found nevertheless, or the 404 page was generated from the core code, as you illustrated.
    Either way, a 404 error wasn’t thrown.

    It might be worth mentioning, that I’m using a jQuery $.ajax() call, which I am now enhancing to handle errors.

    At first, the Ajax call was never running into the error branch.

    Finally, when I overrode the 404.php in the child theme, the Ajax call ran into the error branch, where I now can handle the error softly at a JS level.

    I have no idea, why specifiying the 404.php in the child theme did the trick. (It only holds a small <div> – no <body> or <head>)

    My use-case is solved. We can mark this thread as “resolved” unless you find it interesting for other users…

    Thread Starter arvgta

    (@arvgta)

    EDIT: Sort of solved by adding a custom 404.php in the child theme.

    Now, a 404 error is thrown and the content of 404.php is shown ??

    It would still be interesting to know, why WP throws a 404 error, when a custom 404.php is specified and not in case of the parent theme’s 404.php?

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