pursuitforjustice

Hi @priyankajagtap,

That is fine. I appreciate it. Also, I did try different priorities with the hook, such as the following:

add_action('wcdn_head', 'custom_invoice_css', 20);

add_action('wcdn_head', 'custom_invoice_css', 10, 1);

add_action('wcdn_head', 'custom_invoice_css', 10, 2);

Hi M Rehman,

Firstly, thank you for that very quick update. I tested the admin backend & the frontend, and all CSS appears fine. Great job!

However, I did find other possible errors, and they pertain to the admin backend.

Error #1 — When clicking on admin menus & submenus, the menu link will always not work when clicking it the 1st time. The link will remain “focused” by showing the blue text & underline. Clicking the menu link a 2nd time will go to the link.

Error #2 — Clicking on admin menu & submenu links load slowly. When I deactivate the plugin, the admin menu links load quickly & Error #1 is also not an issue upon deactivation.

Error #3 — There appears to be an issue showing action & filter hooks on the admin backend. The frontend appears to be working, because all hooks will display. However, the backend will become a blank white page when choosing “Show Action Hooks” or “Show All Action & Filter Hooks“. Also, when choosing “Show Hooks Filter” on the backend, the page will not be blank, but none of the hooks display.

I attached multiple screenshots below to give you a thorough overview of Error #3

Screenshot #1 — (Frontend) — How frontend page appears without using plugin features
Screenshot #2 — (Frontend) — “Show Hooks Filter“
Screenshot #3 — (Frontend) — “Show Action Hooks“
Screenshot #4 — (Frontend) — “Show All Action & Filter Hooks“

Screenshot #5 — (Backend) — How backend page appears without using plugin features
Screenshot #6 — (Backend) — “Show Hooks Filter“
Screenshot #7 — (Backend) — “Show Action Hooks“
Screenshot #8 — (Backend) — “Show All Action & Filter Hooks“

Sincerely,
Phillip

@dslyoga , thanks for taking the time to reply!! I’m glad I saved you time, and hopefully I can save others time as well. I didn’t have to exert much mental effort in order to find the bugs and flaws that I’ve already listed. I’m busy during the week, but soon I want to see if I can find any more bugs regarding this plugin.

That post by @dividendninja was truly awesome! I enjoyed it, especially being a poet myself. Who knows, I may end up writing an anti-Gutenberg poem.

Let’s do this Guten-Free diet! I’ve been working with WordPress since 2013. I’m very passionate about it, and I’ve constantly been learning, which is why I’m soo passionately against Gutenberg becoming part of the core. With your experience of 13 years with WordPress, do you have any suggestions where I can re-post this list of issues, so the WordPress Core Team could possibly reevaluate their decision of letting Gutenberg become part of the core?

Additionally, to be fair to the Gutenberg authors (and the WordPress Core Team deciding to let this plugin become part of the core), I understand they are trying to make a post-editor that is in competition of others such as Wix. However, websites are using WordPress more than ever (look at the statistics), so there is no reason to add Gutenberg to the WordPress core, especially considering that most people simply do not like Gutenberg. As the old saying goes, “If it ain’t broke, don’t fix it!”

Cheers,
Phillip

• This reply was modified 6 years, 5 months ago by pursuitforjustice.

Works great!