Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter mgroening

    (@mgroening)

    Sorry for the late answer.
    It just opens an “Add CSS Code” page and creates an Auto Draft in the database.
    It does not replace previous css code.

    Thread Starter mgroening

    (@mgroening)

    Thread Starter mgroening

    (@mgroening)

    When I create or delete a new page everything works just fine. The table with all of my pages looks also correct.

    When I run the query after I create a new custom css without publishing I can’t see any new entry. There is no “Auto Draft”. When I publish it the message “The link you followed has expired” shows up.
    The permalink (when creating a new custom css) always shows /uploads/custom-css-js/202.css at the end. But 202.css already exists. Editing the permalink and publishing then also results in: “The link you followed has expired”.
    The only fix I have found is to refresh the “Add CSS Code” page. After that it shows 223.css which is also the next free post_id in the database. Then it also creates an “Auto Draft” and publishing works.

    There are no problems with javascript: When I run the query after I create a new custom javascript without publishing I can see a new entry “Auto Draft”. And when I publish it, the “Auto Draft” gets deleted and there is a new entry with my javascript.

    Any idea?

    Thread Starter mgroening

    (@mgroening)

    Yes, to see whether it resolves the other issues.
    They are the same as posted by simoptim one week ago.
    So, hopefully the problem will be resolved.

    Thanks for your fast answers!

    Thread Starter mgroening

    (@mgroening)

    With “all the code remains” I mean that after I reinstall the plugin all of my custom code (created with the plugin) reappears in the UI. But as soon as I want to edit or delete them a message shows up and tells me that the file doesn’t exist anymore.

    So I deleted all posts (with post_type: custom-css-js), postmeta and an option entry called custom-css-js-tree:
    a:3:{s:28:"frontend-css-header-external";a:1:{i:0;s:14:"179.css?v=9005";}s:25:"frontend-html-header-both";a:1:{i:0;s:8:"178.html";}s:28:"frontend-css-header-internal";a:1:{i:0;s:6:"78.css";}}
    179.css, 178.html and 78.css were the three scripts that always showed up in the UI even if they don’t exist anymore.
    After that I reinstalled the plugin and cleared my cache again.
    Now they don’t show up again.

    But:
    When I publish a new custom code it still doesn’t show up in the “All custom codes” table.
    And when I first published a new custom css and published a second custom css after that. The first one gets overwritten. It used in fact the same post_id.

    I’m using:
    Wordpress Version 5.2.2

    PHP Version 7.2

    OceanWP Version 1.6.10

    Anywhere Elementor Version 1.1
    Elementor Version 2.6.8
    Formidable Forms Version 4.02.01
    Ocean Extra Version 1.5.10
    Ocean Stick Anything Version 1.0.2
    Simple Custom CSS and JS Version 3.27
    UpdraftPlus Version 1.16.16
    Wordfence Security Version 7.3.6
    WP Extra File Types Version 0.4.3
    WP Fastest Cache Version 0.8.9.6
    Yoast SEO Version 11.8

    Tell me if you need more information.

    Thread Starter mgroening

    (@mgroening)

    Yes, with “crashes” I mean these messages. In my case I think it was caused by the upload of that big file. Big in the sense of many lines (3200 lines, but only 80 kb). Sorry, I forgot to describe it in more detail.
    I also tried to increase post_max_size, but it did not resolve the issue.

    I found out that my code is also in the database under posts. Everytime I create a new file it gets stored there and is also created in the uploads/custom-css-js directory.
    Except html files: they are not stored in uploads/custom-css-js. I think that is intended, right?

    I don’t know why but sometimes the post id in the link for editing or deleting a custom css/js/html doesn’t match the post id in the database. So I get error messages, like “The link you followed has expired” or “The file doesn’t exist anymore…”
    (e.g. post id 99 in the link: https://example.com/wp-admin/post.php?post=99&action=edit but it is 101 in the database)

    So I cleaned up my database, but the plugin is still not working correctly.
    If I create e.g. a new css it does not show up in the “All custom codes” section. I have to change the filter to “CSS Codes” to see my new file.
    And I cleared the cache and reinstalled the plugin again, but still…

    • This reply was modified 4 years, 7 months ago by mgroening.
    Thread Starter mgroening

    (@mgroening)

    Yes, I tried that multiple times and it uninstalls the plugin but all of my code remains.
    It seems like my html/css/javascript code is kind of corrupted. And it causes the plugin to crash everytime when I use it.
    I think this behaviour started after I tried to publish a very big css file in this plugin.
    Do you have any recommendation what else I can do to repair the plugin?
    Maybe you can reproduce the problem by uploading a huge file.

    • This reply was modified 4 years, 7 months ago by mgroening.
Viewing 7 replies - 1 through 7 (of 7 total)