EkoJR

Yea, for now I’m going to leave this un-resolved until I can create a shortcode param that can properly re-size the image.

Since 0.3.Beta5, this feature has been added to the plugin. Re-reading your post, I may add an option later to dynamically add users based on their roles. For now, the setting is available for webmasters to utilize.

If your currently not a user of the plugin, I highly recommend trying it out again since many other settings have been added.

Sorry, most of my work has gone into a lot of the backend portions of the plugin, and just a little bit here and there on the frontend. So there’s some areas that didn’t have much information to go by. Beta 5 I tried to fill in a lot of the gaps by adding more info dialogs to click on.

Yea, for the most part, I have certain keywords set up for the community to initially go by, and use just the keywords needed to point to with function and/or setting. This is probably because of a programming habit to catalog things based on their main function and sub-category. Some of examples would be ‘Require Taxonomy’, ‘Require Terms’, and ‘Include Terms’ in the post_type/taxonomy section.

Another reason for doing that is because I’ve noticed there’s a lot of diversity in the languages that the community uses. The more keywords there are, the more chances there would be a mis-communication in translation. When I have 0.3 stable, I’ll be able to switch my primary focus to providing a decent knowledge-base.

Sorry, I hope I understood you right. Which, by the way, what did you mean by

You will see on pp soon

What I was trying to explain is that there is a setting to require the taxonomy within the post type, and if no other terms/taxonomies are being used within that post type. Then an error will be thrown since only one taxonomy is being used.

Anyways, thanks for appreciation for the plugin. I just released a new beta version which has much more additional settings to take advantage of. Most of the filters from WP_Query are now part of the plugin’s filters. Hope you enjoy the recent upgrade =)

Sounds like you have a ‘Require Taxonomy’ checked when no other taxonomies are being used within that post type.

Actually, one way to fix this is to use inline styling. The only problem is, if the dimension ratio isn’t the same, then some pictures would seem stretched in one way.

The option I usually resort to is using the width and/or height style. <img src=[post_thumb] style=”width: 100px;“/>

There was another response simular to this in [resolved] Result-Layout. However, I don’t have anything setup to grab a certain size. All the shortcode does is grab the picture that you had uploaded with the original size.

Yes you can, and you can include other terms within the taxonomy depending on what page is currently being viewed.

Glad to see that it works as you expected. There is one problem though that you may already know about. The picture aren’t cropped, so you have to try and match the ratio. Otherwise the pictures will seem stretched out. Other than that, things work fine with changing the size.

Right now I don’t have the feature available, but I will be doing some work within the shortcodes in the not too distant future.

Well, right now I’m kind of in a poor position to provide a proper reply since I’m in the middle of development, but I’ll try my best.

When applying your content within ‘before’, ‘content’, and ‘after’ (btw, working on a custom exit message if no posts are found), you can also add CSS for ids and classes, or you can use the inline styling. I prefer inline styling since other CSS code usually can’t interfere with inline (sometimes it does though, especially if it’s in some JavaScript coding). Unfortunately there are some issues with excerpt shortcode, but you can use the param in it to shorten the amount of wording. In some instances, it doesn’t work properly though (manual excerpts in one of em).

Anyways, this should work for ya, but you may need to edit some of it to your style.

Before
<div style="">

Content
<a href="[post_permalink]"><img src=[post_thumb] alt=[post_title] style="float:left; width: 100px; margin: 0px 5px;" hspace="5" vspace="5" /></a><h2 style="margin:0px; font-size:200%"><a href="[post_permalink]">[post_title]</a></h2><p style="font-size:70%; margin-top:0px;">written by [post_author]</p><p style="font-size:100%;">[post_excerpt]</p>[final_end]<hr/>

After
</div>

While debugging, I wasn’t able to reproduce the results, but after researching I’ve found that it really isn’t necessary to use the WP reset functions in the manner the plugin uses it. Plus, there have been issues reported when wp_reset_query() is placed on a home page or front end page. The function itself is made to reset any modifications made to global $wp_query (custom variables are separate from globals), and for some reason the query variables were being integrated with the main query. So I’m stripping that out. As for wp_reset_postdata(), I plan on just taking that out as well. The 2 functions do effect the globals, the plugin doesn’t use anyways.

It was something I added during development, and just left in. I probably should of just left it out before the release. When I start modifying the shortcode section though, I’ll more than likely add wp_reset_postdata() back into some code, but I’m pretty sure it was wp_reset_query() that was causing the issue.

If you would like to test theory beforehand and check for the issue, then I have a link under Other Files on a development page. It would help me out as well knowing what might happen for future development. Anyways, thanks in advance.

APL 0.3.b5 Development Page (subject to change after release)

After some time getting all the core features set into place, I also decided to tackle this subject in the 0.3 release. So far, everything is in working order as of 0.3.b4. Sorry about the issue though.

It’s no problem, thanks for the reply back. I was beginning to worry, but I’m just glad we were able to find a fix for this, and have an available fix for others. I’ve been doing some work on the plugin, and I was waiting on to see what your results would be so I can make some more adjustments as well as further investigation into it. I have a couple of ideas why this is error is happening.

So for the most part, I would recommending continuing staying up-to-date with the plugin. There’s many more features and settings along the way, and I’m also planing on staying up-to-date with WordPress, and I probably won’t be supporting older version in the process. If I do, it would probably be because of multiple requests. The best thing that helps is when others report issues. Kind of a blessing and a curse.

Getting back to the point though. I think this could be happening in 0.3.b4 because themes typically use the WP_Query class as well as global $post, and in the process. Even though I’ve been trying to keep the data seperate, I may unintentionally integrated it with global $post when using wp_reset_postdata(). After some looking into, I may want to add wp_reset_query() back since it is made for using multiple queries. I was just trying to hit 2 birds with one stone in this case.

I don’t have any solid information as to why this is happening, but I will keep you posted.

Np, thank you for posting this btw. Last night I ended up finding a bug that your setting was able to display. So I’m working on getting another version out sometime within the next few days.

I tested this out on my localhost, and I see what may be the problem. Cause I see somewhat the same issue you described.

Although, my first theory was that the table was too big and it was getting overlapped, but it doesn’t explain why the whole border is missing. The problem that I ran into with my test site is the theme CSS styles were taking over some things.

Could you link the URL to the page that your having the issues on. I might be able to figure out what exactly is going on.

Anyways, glad you enjoy the plugin, and thank you.