• Resolved Gal Baras

    (@galbaras)


    Changed: Refactor some occurrences of “plugins_loaded” replacing it by a new action: “plublishpress__loaded” which runs after the requirements and libraries are loaded, but before the plugin is initialized;

    I can’t find plublishpress__loaded in the code, and it looks like a typo (or two), but I can’t find publishpress__loaded or publishpress_loaded either.

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    Hi @galbaras

    Thanks for using PublishPress Series.

    There are multiple places where we added it. You can view the changes here: https://github.com/publishpress/publishpress-series/commit/86420691706f09fb8810f8b7e57ab7159db2ca2b

    Hope that helps.

    Thread Starter Gal Baras

    (@galbaras)

    I can’t find a single occurrence of plublishpress__loaded on the page ??

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    @galbaras Can you let me know what you are trying to achieve here?

    Thread Starter Gal Baras

    (@galbaras)

    Just checking the listed change, because it seemed strange, and because changing action hooks can cause issues.

    Plugin Author Olawale Adesina

    (@olatechpro)

    Hello @galbaras

    We didn’t change hooks that could have effect on third part or plugins usage.

    All changes are internal usage and in this case, while trying to refactor the plugin to fix some issues related to library conflict and migrating the plugin vendor to an internal vendor, we made sure plugins_loaded is only used once in the plugin and that explain while there’s replacing ‘plugins_loaded’ in the changelog.

    In case of series, the name slightly changed to publishpress_series_after_init to reflect the need for the other action previously hooked to plugins_loaded to be changed to publishpress_series_after_init and this new action is loaded inside the only plugins_loaded in the plugin.

    In practically, they still run inside plugin_loaded just that they do when we want them to which is after the plugin init.

    Nevertheless, they changes are internal plugin usage changes and contrary to what you said, they have no serious or any implication with any other thing neither did we changed original hook usage for others.

    Regards.

    Plugin Author Olawale Adesina

    (@olatechpro)

    Hello @galbaras

    We didn’t change hooks that could have effect on third party or plugins usage.

    All changes are internal usage and in this case, while trying to refactor the plugin to fix some issues related to library conflict and migrating the plugin vendor to an internal vendor, we made sure plugins_loaded is only used once in the plugin and that explain while there’s replacing ‘plugins_loaded’ in the changelog.

    In case of series, the name slightly changed to publishpress_series_after_init to reflect the need for the other action previously hooked to plugins_loaded to be changed to publishpress_series_after_init and this new action is loaded inside the only plugins_loaded in the plugin.

    In practically, they still run inside plugin_loaded just that they do when we want them to which is after the plugin init.

    Nevertheless, the changes are internal plugin usage changes and contrary to what you said, they have no serious or any implication with any other thing neither did we changed original hook usage (in WordPress context) for others.

    Regards.

    Thread Starter Gal Baras

    (@galbaras)

    Got it. I could verify the change on Github, but the plugin still has plugins_loaded in several files under lib/vendor/publishpress and the changelog still has a typo and a formatting issue (<name> is taken as a tag).

    Plugin Author Olawale Adesina

    (@olatechpro)

    Thanks @galbaras

    The lib/vendor part you mentioned is a vendor library.

    If you need to understand how our code work, kindly take your type to explore the repository.

    Support is meant to attend to issues found in the plugin.

    Regards.

    Thread Starter Gal Baras

    (@galbaras)

    This makes sense (now).

    The changelog still has a typo and a formatting issue due to the use of angle brackets. Maybe you can take a look at it?

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    @galbaras Which typo and formatting issue on changelog you are referring to?

    Is it this one: https://www.ads-software.com/plugins/organize-series/#developers ?

    Thread Starter Gal Baras

    (@galbaras)

    Yes. "plublishpress__loaded" should be publishpress_<name>_loaded (no “l” after the first “p” and the angle brackets should be HTML escaped. See your readme.txt file on Github.

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    @galbaras Ah, we did missed this. Thank you for your report. I’ve notified our developer about this.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘New plublishpress__loaded action’ is closed to new replies.