Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author David Decker

    (@daveshine)

    @trogg71:
    Hi Bernie!
    Thanks for your feedback and letting me know.
    I assume it’s because of some typo/wrong name I had in the file.
    I have attached a tweaked file for you to test it out:
    https://www.dropbox.com/s/0nycgudffncsllh/gcedd-frontend-file-testing.zip
    –> Download it, unzip and upload that file via FTP within my plugin folder:
    wp-content/plugins/genesis-connect-edd/lib/gcedd-frontend.php
    You can override the existing file.

    I hope this resolves it. (If not this would require further testing and/or rewrite of post meta for this…)

    Thanks, Dave 🙂

    Hi David, I’m having the same problem and the fix didn’t remove the notice/error.

    Plugin Author David Decker

    (@daveshine)

    @jean Galea:
    Thanks for your feedback!
    User “Trogg71” never responded back so I could do no further stuff until now.

    My question for you is, what other plugins do you have installed:
    Also the same “Wiki” plugin from WPMU DEV as the other user above? You can also send me your list in private via http://genesisthemes.de/en/contact/ or the EDD system info file if you want…

    Can you also describe when the error appears? Only on frontend? And when, when viewing taxonomy archive, a single taxonomy term or always?

    This would help me locate the bug and bring a fix soon!

    Thanks for your support!
    -Dave 🙂

    Plugin Author David Decker

    (@daveshine)

    @trogg71 & @jean Galea:
    I just have created another file tweak for you both to test:
    https://www.dropbox.com/s/v0f2djohw2uo9lr/gcedd-frontend-file-testing_v2.zip
    —> Same procedure as above: override /lib/gcedd-frontend.php with the above unzipped file…

    If that works I can release an update.

    Thanks, Dave 🙂

    Plugin Author David Decker

    (@daveshine)

    I was told by @jean Galea that the issue was fixed with 2nd test file. This fix went straight into version 1.3.0 of the plugin which recently got released! 🙂

    Issue fixed & topic resolved. Thanks, Dave 🙂

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

The topic ‘Taxonomy error’ is closed to new replies.