twirth5

I wish to report a false alert as the plugin started working as advertised.

I do wish that the posts were sorted by date (rather than sticky status) but we will become acclimated to it.

Thank you for your hard work.

Link to pic

https://drive.google.com/file/d/0B_D711o-S0YPVWdOLUJDeFAxTzg/view?usp=sharing

Hueman Pro theme with JetPack. The pic shows what I would like to accomplish. I cannot find a solution anywhere.

Thanks for the prompt response but up until a week ago, I could apply post type, category and tag filters to a replace function. Now QFI skips right past that step.

Perhaps this feature is now only available in a Pro version?

Thank you for the fast response!

I could not locate any PHPInfo files to edit so I did some research and that told me to add max_execution_time to php.ini in the root of my host server.

php.ini contents:

upload_max_filesize = 64M
post_max_size = 64M
max_execution_time = 300

I did this and in the process of trying it out. I will increase the time if bulk optimization still fails.

Please alert me if I am going in the wrong direction here.

Best regards,
Terry

Thank you Jeremy.

I wrongly assumed that file structures were similar regardless of the theme.

Thank you Jeremy.

Besides WP QUADS, Jetpack and the hueman theme, I do not have any plug-ins that add content to post pages, and they all worked fine together until recent updates.

That said, will there be any problems if I deactivate/activate Jetpack in order to see what happens?

Otherwise, the links that you provided with code to move the pagination controls are intriguing but look intimidating to this amateur coder. I will have to study it pretty intensely and am quite fearful of mucking everything up during the revision process. For example, the instructions say “add XYZ” but rarely say “edit XXX.xyz and add XYZ here.” This means that I have to search through various files in order to find the location that is being referenced in the instructions. It is obvious that experienced coders know where all the code is located to begin with but not so much with us self-learners.

Nevertheless, thank you for your hard work.

Sorry for butting into the thread but it is the exact same problem I was having. From now on I will start my own issue.

Lesson learned and will not mark resolved.

They must have been added via Jetpack then. On the other hand they are turned off.

Will pursue this issue from the Jetpack side then.

Thank you once again for your hard work.

Yes, in the Settings section of WP Admin.

I can turn these settings on or off at will but the hueman related posts and navigation controls do not show up when enabled, even when related posts are turned off in the WP Settings menu.

We have been through this before and I found that the hueman related posts option works better with pagenavi than those found in WP Settings.

Something must have changed in one of the hueman updates.

I also have this problem with hueman single post settings as neither related posts nor post navigation controls show up.

I am experimenting because the settings>reading>related posts and settings>sharing>share/likes options push the pagenavi controls way down the page.

FYI the related post option is deactivated in settings>reading.

Thanks again.

Instead of messing around with Jetpack and code, I decided to deactivate the Jetpack features that are also built into the hueman theme and try those instead (like “related posts”).

Now the bottom of the page is now much cleaner and the pagenavi controls are much closer to the bottom of the post.

It appears that overlapping Jetpack/hueman features compete for screen space. It is also apparent that hueman was created with pagenavi in mind.

Case closed.

That is impressive! Thank you for your hard work.

Unfortunately, the new code didn’t accomplish anything.

Fortunately, the page looked exactly the same so there no collateral damage–but I restored single.php anyway.

Maybe I need to poke around in the Jetpack forums?

As usual, thank you for your rapid response!

https://wp.me/p76U8a-8LJ

That did it!

Thank you for your quick responses and hard work.

Case closed . . .