Viewing 23 posts - 31 through 53 (of 53 total)
  • Author
    Posts
  • #1067505

    Hi,

    See private content.

    Best regards,
    Günter

    • This reply was modified 5 years, 9 months ago by Günter.
    #1067516

    Hi,

    log2.txt shows the problem:

    If you look at the first 2 arrays: The second one is the internal shortcode tree that is generated when saving the post. It shows 1 entry.
    But the post content has 2 shortcodes: av_masonry_gallery and av_image.

    I activated the ALB debuging mode – you have a button Show Parser Info – this opens a new window and there you find a tab Shortcode tree. It is correct stored.

    I extended the logfile output.

    If I copy the post content to my dev environment it does not trigger any error (even with YOAST active).

    Did you already try to deactivate the Classic Editor plugin – you should not need it. You have a theme option for that (Theme Options tab).

    Best regards,
    Günter

    #1067523

    What I had been doing was using the classic plugin and disabling it in the theme. The reasoning was that, this was the setup when we were getting the fatal errors. I have now disabled the classic editor plugin and rest Enfold to use the classic editor. (Does anyone besides WP like the block editor?)

    Part of the issue there also was that in 4.5.2 or 4.5.3 the screen options were not there for the enfold classic editor but they were for the plugin version. That has since been fixed/changed in 4.5.4.

    On the MichaelAlbany.com site a raw text file is showing under the Avia Builder sections. This does not show on any of the other sites. Is this part of your code?

    On the ALB Debugging, again, not within my knowledge range. Don’t know how to find it let alone use it!

    More in Private Content

    I appreciate all you’re doing here!

    #1067709

    Hi,

    I found the bug.

    I updated 3 files for you on 1 site:

    enfold\includes\loop-index.php
    enfold\includes\loop-page.php
    enfold\includes\loop-portfolio-single.php

    I left the logfile script in enfold\config-templatebuilder\avia-template-builder\php\shortcode-template.class.php.

    I deleted the old log files, but I think there should be no more errors coming.

    Can you check that everything is displayed as it should.

    If we do not see any more log entries you can revert shortcode-template.class.php to the original.

    For the other sites please update the three files with the files in this folder:

    https://github.com/KriesiMedia/enfold-library/tree/master/temp_fixes/Enfold_4_5_4/Fix_undefined_index

    Thank you for allowing us to use your site – it was a great help.

    I also removed the debug mode setting – so the additional textfield is not shown any longer (is part of the debug and shows the shortcodes generated by ALB).

    The fix should be in the next update.

    Best regards,
    Günter

    #1067852

    Hi Gunter,

    I updated all sites with the files provided and I have disabled WP-debug on all sites previously. The only error logging is the coded ones you provided. I will monitor those for a day or two to see what happens before reloading to the original shortcode-template.class.php.

    I didn’t get to this until 12:54 GMT because when you first posted I was literally walking out the door. Sorry for the delays.

    It was my pleasure to help get this fixed. I enjoy the collaboration! Anytime you want to look at something or test something on these site just let me know, I will create a backup and get you the accesses you want/need. Being the owner of 30 licenses of Enfold kind of gives me a vested interest! LOL

    I will let you know what the final verdict is Monday morning my time. I am GMT -5.

    #1067918

    OK I did something wrong. The site you updated, no new errors. the sites I updated, still have issues.

    See Private Content

    What did I do wrong?

    #1068349

    Hi,

    Just seen an error in conjunction with a REST API call (…./wp-json/wp/v2/posts/).

    Checking for a fix for that.

    Temporary I uploaded the latest version of Enfold including the latest fixes to the avia_logfile directory.
    If you want you can update your other sites with that. I will let you know when the REST API problem is solved.

    Best regards,
    Günter

    #1068387

    Hu Gunter,

    OK you lost me. All sites are running 4.5.4 so is that what you’re thinking when you say, “If you want you can update your other sites with [latest version of Enfold including the latest fixes to the avia_logfile directory.]” or should I be copying the avia_logfile directory and pasting that into the other sites?

    Thanks!
    Michael

    PS – Just a humorous note, it has taken me until this post before my computer learned that your name does not have an “h” in it! LOL All notes above that say Gunther, I blame Apple’s auto correct. ;-)

    #1068474

    Hi,

    I uploaded enfold.zip in the avia_logfile directory – download this file, unzip and update your other sites via FTP.

    That file contains the latest fixes not in 4.5.4 – it should work now without notices except for REST API calls – these still produce errors – I’m currently working on this.

    Best regards,
    Günter

    #1068477

    Got it. I will update them now.

    Thanks again!

    • This reply was modified 5 years, 9 months ago by MichaelAlbany.
    #1069943

    Gunter,

    The one site you have been working on directly (Private Content) is the only one sill returning errors, the rest of the sites seem to have calmed down. The error though looks more like code than an error though. Below is the most recent entry in the error log.

    Your thoughts?

    Michael

    Error Code:

    20/02/2019 13:51:59: shortcode_handler_prepare – $meta[index] not set for av_masonry_gallery
    Frontend: https://michaelalbany.com/i-owe-you/
    SERVER[‘REQUEST_URI’]: /wp-json/wp/v2/posts/
    shortcode_index: 10
    Ajax: No Ajax Request
    REST: REST Request
    fake: 1
    fake1:
    meta1:
    Array
    (
    [el_class] => avia-builder-el-10
    [index] => 10
    [this] => Array
    (
    )

    [siblings] => Array
    (
    [next] => Array
    (
    )

    [prev] => Array
    (
    )

    )

    )

    meta:
    Array
    (
    [el_class] =>
    [custom_markup] =>
    )

    tree:
    Array
    (
    [0] => Array
    (
    [tag] => av_one_full
    [content] => Array
    (
    [0] => Array
    (
    [tag] => av_heading
    [content] => Array
    (
    )

    [index] => 1
    )

    )

    [index] => 0
    )

    [1] => Array
    (
    [tag] => av_one_third
    [content] => Array
    (
    [0] => Array
    (
    [tag] => av_textblock
    [content] => Array
    (
    )

    [index] => 3
    )

    )

    [index] => 2
    )

    [2] => Array
    (
    [tag] => av_two_third
    [content] => Array
    (
    [0] => Array
    (
    [tag] => av_image
    [content] => Array
    (
    )

    [index] => 5
    )

    )

    [index] => 4
    )

    [3] => Array
    (
    [tag] => av_one_fifth
    [content] => Array
    (
    )

    [index] => 6
    )

    [4] => Array
    (
    [tag] => av_three_fifth
    [content] => Array
    (
    [0] => Array
    (
    [tag] => av_contact
    [content] => Array
    (
    )

    [index] => 8
    )

    )

    [index] => 7
    )

    [5] => Array
    (
    [tag] => av_one_fifth
    [content] => Array
    (
    )

    [index] => 9
    )

    )

    #1070320

    Hi,

    Thanks for your feedback.

    It is the REST API call /wp-json/wp/v2/posts/ that still produces the error. I’ve been working on that the last days – turned out to be complex. But I’m currently testing the solution and it seems that I could fix the problem. As soon as I’m ready I upload the version to your server so you can test it.

    I hope it will be today. I let you know.

    Best regards,
    Günter

    #1070324

    Got it. Just an FYI it is only happening on the one site if that helps.

    #1070368

    Hi,

    Just uploaded 2 files in avia_logfile directory:

    enfold_4.5.4.1.zip is “real” version
    enfold_4.5.4.1_log.zip is with logfile output.

    Could you use the log version on the site I worked on – delete log.txt after install. Hopefully no further messages should come up.

    Keep a backup of the 4.5.4 for fallback.

    Have a nice weekend and let me know if it works.
    Thanks once again for your cooperation.

    Best regards,
    Günter

    #1070371

    Done. I will let you know how it goes. Have a beer on me this weekend!

    #1070377

    Hi,

    Just have opened one :)

    Best regards,
    Günter

    #1071095

    I have review the log files, or should I say lack there of. I am still getting I/O spikes of some kind but they are minimal. Not sure they are even related without some type of log. No fatal error means no real log entry so…

    I also updated one site to WP 5.1 for overnight observation.

    #1074078

    Gunter,

    It seems that something is fixed and something isn’t. There are no more error logs being created so that is the good news.

    The bad news is that I am still getting IO spikes and GoDaddy is still biting the site as being “limited in the last 24 hours”. I am not even sure this is still an Enfold issue as without some type of error log I am at a loss on how to track it down.

    Some details in Private Content.

    #1074265

    Hi,

    Great to hear that there are no errors logged.

    Can you check with your hoster if they can figure out what requests cause the I/O spikes ? Maybe some robots are trying to attack your site ?

    Do you have an idea about the REST API calls – they could be done by robots.

    Best regards,
    Günter

    #1074367

    GoDaddy was not helpful. Their answer is that there are too many images. I am a photographer by trade so, obviously. They said spend money, upgrade to a plan with no limits. I am thinking it may be SPAM bots as my spam firewall (CleanTalk plugin) is getting about 350 attempts a week. I have seen as many as 1200 in a week, mostly from Russia.

    I don’t know about REST API calls but I can spend the day learning!

    Thanks for all your help!

    #1074788

    Hi,

    Maybe you shoud consider to change the hoster to one with a better standard firewall. I can imagine that a site with good photos is interesting to hack.
    REST API calls return jsoin data which normally is only usefull for applications to get the page content and use it in JavaScript for further processing.

    Best regards,
    Günter

    #1074901

    Gunter,

    Where ever you are, if I am ever there I am going to buy you many beers!

    I am kind of stuck with GoDaddy for now. I will deal. Clean Talk just this morning added a new PHP Offsite Error logging. I am going to check that out. It also has a firewall that I haven’t been using, so…

    Thanks again!

    If you ever come to Philadelphia USA, beer is on me!

    Michael

    #1075023

    Hi,

    Welcome. Glad we could help you.

    Best regards,
    Günter

Viewing 23 posts - 31 through 53 (of 53 total)
  • You must be logged in to reply to this topic.