Olawale Adesina
Forum Replies Created
-
Hi @yolandal We’re currently investigating this issue and trying to provide a solution as soon as possible.
Can you confirm the number of checklists you have enabled for the post?
@jackhnhh We do have a report of the page slowing down or hanging after clicking “Update” on a post which we’re trying to work on but for this Autosave, we’re not able to trace the issue as we don’t have autosave feature or function on checklists.
If you’re not able to provide a screen record to help with the investigation, I’ll hope it’s related to the issue mentioned so you can try an update we’re working on again.
Checklists doesn’t really have a function that trigger Autosave feature.
Please compare with when you have checklists enabled and disabled editing same article and a screen record will help.
Hi @jackhnhh, Can you confirm you really have version 2.10.1 and not v2.10.0?
Hello @jackhnhh We just released Checklists v2.10.1 targeting your reported issue. Can you test and confirm if it fixes the problem?
Hello @infinitnet We just released v2.10.1 targeting your reported issue. Can you test and confirm if it fixes the problem?
Hi @wireduk
We’re using ppc_last_visited_page to determine last visited page for Roles > Redirect users to the URL they were viewing before login feature.
We’ll be adding a configuration to only limit it for site that enable this feature and select the option based on your report and as mentioned in https://github.com/publishpress/PublishPress-Capabilities/issues/933.
Regards.
Hi @heyjesshuff
Thanks for the information. We’ve been able to replicate this issue and working on a fix which we’ll get to you on Monday considering it’s the end of the week today
@spabav Apologies for the delay in getting response.
We’ve Identified this issue and working on a fix to enable successful metadata migration which will be sent to you hopefully on Monday for testing and confirmation purpose before we release an update.
Regards
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.
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.
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.
Hello @laxman-prajapati Can you try this version and confirm if it fixes the issue to enable us roll out an update
https://drive.google.com/file/d/1FIf6TINAXXCrpuMKWV_SdFYSCltutD1M/view?usp=sharing
I think you may be having capabilities issue.
- Confirm if manage publishpress series is enabled for your role as shown in the below screenshot
- Can you install https://wordpress.org/plugins/capability-manager-enhanced/
@wp-mememe Did you get this message after running the upgrade?