skinner009

Thanks for the idea. Gave it a lot of thought and was still worried about editing capabilities, so I think the short path is to use permalinks to assign a really unique URL string to each of the posts, all restricted to Logged In and above to read. This way they will technically be readable to anyone at Logged In (Customer) and above, but no one will be able to guess the string (/second/month/ID/title) even if they know the title of the post. The access point to the posts is above Customer.

And now there is no way the author of each won’t be able to edit it. We shut off RSS and archive and won’t allow Google indexing, and are hiding search except above Customer, so I think the posts will remain hidden except to above Customer. Knowing the ID of a post and how to view it would be a backdoor but this isn’t critical info and who out there would bother to do that for no gain. Anyway, been a really interesting puzzle, thanks much.

I did, it was no help. I had to hire an outside dev to fix a flaw in your product, that you wrote, and you still sell.

• This reply was modified 3 years, 1 month ago by skinner009.

All good, thanks very much, great response

OK, if I get time in the next few weeks I’ll see what happens in a test environment first, thanks. You’re right though, I tried it without the Cron and the posting performance tanks, so it’s either Cron or nothing.

• This reply was modified 7 years, 1 month ago by skinner009.

I’ve been following this issue too, and for most sites there is no reason for the plugin to fire a query every few seconds. How about once an hour?
How about a setting for it? How about making it compatible with a stock Cron install instead of asking for every user to customize their core structure for it?

The developer’s suggestion to re-set-up our entire Cron process is way, way too much (think of the issues we cause with all other scheduled tasks) to accommodate one plugin. The idea that one plugin, again, great plugin, but it needs to run as light as possible, is in there taxing resources every few seconds seems like a deal killer for me. I hate to give this up, but am losing faith.

Hi Hesham, I’m using the Nootheme Jobmonster theme, so the posts are custom posts. the beta site is beachjobs.org

I would be willing to pay for help to get this done, I have looked at the instructions but have no experience with this. thanks!

I agree, and I don’t think it’s your plugin, see: https://www.linkedin.com/company-beta/11160978/

This is happening after a front end submission, when the user posts a job listing, (which is a custom post), so it’s all tied to everything that happens to that, and then swirling in the 3 autopost plugins. It takes about 5 seconds to build the job post, I was thinking I could try to reorder how it happens, but it’s not that big of a thing at this point. Thanks for the reply, keep up the cool work.

-g

That works better, not that I don’t want to give credit, but it does open a big gap under the widget. I might try to put a little text credit under the daily forecasts.

Thanks again Hal.

-gs

Perfect solution, thank you Hal. And yes it is showing the forecast days.