arollettson

Hi Riza,
Turns out that my post was unfortunately premature. Bearing in mind that publishpress is completely integral to our site work flow, my attempts to enhance access to different categories of user via ‘Capabilities’ pluging resulted in a coincidental link between my attempts to make changes, and the on-again off-again behaviour of emails sent/not sent which were meant to be triggered by editorial comments.

Never having a need to use the notifications log in Publishpress, it took me a while to find it. The problem continued to reoccur all day yesterday, even after Iremoved the capabilities plugin completely.

The problem was tagged in notification log as ‘Failed X: Error: The notification was set as “Scheduled” but the cron task is not found
(asynchronous)

This would therefore appear to be a problem not of ‘Capabilities’ plugin, or for that matter the ‘PublishPress’ plugin, but either WordPress itself (which I updated day before yesterday to 6.1), or more likely my host.

I’m cautiously optimistic that the problem, (which settled down late in the afternoon yesterday, has fixed itself. Work today has not required inter-staff emailing yet.)

Hi Pubudu,
Forget this request. I think I had the Awaken Theme activated by mistake instead of Awaken Pro.

With Awaken Pro activated, I had created the ad for the header and installed it in the ‘header area’ available in widgets. Then at some point in experimenting with various things, I activated ‘Awaken’, which does not show the ‘header area’ location for widgets, but continued to show the advertisement itself. By then, I’d removed the offending widget from the database, but I’m sure there would have been no trouble, the moment I reactivated the Awaken Pro Theme, which would have allowed me to remove the widget properly.

Cedam.

I wrestled with this for some time and came up with a solution. The theme author is aware of the problem, and at least knows how I solved it. Hopefully he’ll release an update that provides some sort of on/off switch

As you will know, the default featured image will not show up on your single ‘original’ post, unless you specify one. However, the default image shows up on all auto generated smaller summary posts in various 2 column and 3 column magazine views, including the Awaken Pro theme’s ‘related posts’, whether you asked for an image or not.

If this is your problem . . .

Fixing the problem is a little tiresome until the developer provides an update that gives a better fix. What you can do search through all files of the plugin for ‘thumbnail-default’. This will also find instances of ‘mini-thumbnail-default’ which you may need to address, too. There are about 16 places in 10 files in the Awaken Pro theme, fewer instances and files in the Awaken theme. In each case, the thumb-nail.jpg is given as a file reference for an <img tag. Insert a class statement, such as class=”thumb-default”,
immediately after the <img tag (the result should look like <img class=”thumb-default” [then whatever comes next].

You can then go to Themes/Customize/Site Styling/Custom CSS

and add the following CSS statement (make sure you include the period at the head)

.thumb-default {
display:none;
}

This will turn off all default images.

display:block; will turn them all on. There is no individual selection method. If you turn them all off, however, you will be alerted to missing image files that you might have been expecting to be there by a broken image link symbol, and the filename of the missing link.

If you have uploaded an image, and it has been selected and is visible on your single post, but not on your smaller autogenerated magazine view posts (and you are getting a broken image link symbol, then you should try the ‘regenerate thumbnails’ plugin, which rebuilds all the necessary smaller views of your original post.

Hope this helps

Alan

Oops,

Okay, I see that I missed the switch in the widget box to turn on hierarchy. The second issue is still a problem, which I imagine can be simply solved by automatically checking the parent category whenever a sub-category is checked

Thanks for getting back to me Pubudu. I have not explained my problem clearly.

I have posts without any images. In a single post page, these posts display fine — headline and text. Thats all I have, thats all I want displayed. But in magazine form autogenerated posts,’image not available’ images appear above these posts . Of course images are not available. I didn’t have an image to support the post. And I do not want an image to support any view of the post, particularly not an image that says ‘image not available.’

In a world in which more and more people are paying attention to copyright, I cannot afford to run a blog and ‘steal’ uncleared images. Since Creative Commons helps out a lot with images, I have modified the featured-image-caption plug-in to provide an ideal Creative Commons photo attribution, as well as a caption. In spite of this, it is simply not possible for me to find or shoot images for all my posts.

To avoid displaying these unwanted ‘image not available’ images, I have temporarily stripped all your references to thumbnail-default and mini-thumbnail default from your files — thats approximately three lines of code in approx. twenty places over approx. ten files. Hardly an ideal situation. Particularly if I have to repeat it for every update.

In a future release, helping my blog look more professional (without all these unnecessary ‘image not available’ images) could be accomplished by a simple switch to turn on or off display of these images, either a general switch for all or a post-specific switch (better).

Incidentally, when I want and am actually using featured images, together with photo captions below them, the ‘featured-image-post’ plugin allows captions to be posted only below single blogs. This is great, because a photo attribution with three links — photo, artist, and license — cluttters up smaller auto-generated posts horribly in two and three block auto-generated magazine pages, particularly since your auto-generation code strips out formatting which I use to reduce the size of the caption.

However, some of your smallest auto-generated posts — (which call in the mini-thumbnail-default) are seen by the ‘featured-image-post’ plugin as single posts. So the caption is left in on these tiny magazine posts, producing an absolutely horrible mess. The unwanted featured image caption is displayed as virtual nonsense, it is so large and lengthy compared to the tiny images. That means I can’t use your smallest post images at all, though at the moment, everything else is working for me.

Ensuring that captions do not display on these smallest posts (including the ‘you might be interested in the following’ posts) would be really useful. I’ve noticed that your code is a little bit different around these posts, but haven’t tried to figure out why they display, when others don’t.