Eric Teubert
Forum Replies Created
-
You can’t mix category=”…” and query=”…”. As you need the latter for the post_type, you should just add the category there.
Not sure about your problem. If you have a custom post type called “book”, you could display them like this:
[archivist query="post_type=book"]Yeah. The query solution would have been
[archivist query="cat=1,43"]Your HTML is not valid.
You added a third td in the tbody but there are still just two th in the thead. You open the second td but never close it.
Have a look at my fix: https://gist.github.com/1909358
Please paste your code again using pastebin. A moderator seems to have deleted your code.
Please paste the archivist template you are using. If you have an example page, that would be helpful too. The behavior of the display might be influenced by the WordPress theme you are using.
Don’t know, I just set it to resolved.
Original Question: http://wordpress.org/support/topic/plugin-archivist-custom-archive-templates-can-not-wrap-excerpt
Well, not quite 🙂 That’s just an example code snippet for plugin or theme developers to get an idea how to implement something like that. I’ll try to implement it when I find some spare time.
The WordPress API doesn’t allow something like “the last x days/weeks/…”. You can only query for a certain date/month/year as shown here: http://codex.wordpress.org/Class_Reference/WP_Query#Time_Parameters
[archivist query="category=streaming&year=2012&monthnum=2&ignore_sticky_posts=1"]strtotimeis not supported by the WP_Query API. I might be able to add that functionality to the plugin but it’s not trivial. Don’t hold your breath.My fault, I forgot to add the new file I added to the repository … quite embarrassing. Fixed in 1.4.1.
Hi Cris,
do you have access to your PHP error log? There must be an error breaking the script after printing the “before template” part. It would help me to figure out the bug.
Furthermore, could you please paste the shortcode you are using?
PHP 5.2 compatibility is restored now in version 1.4.
PHP 5.2 compatibility is restored now in version 1.4.
Hi Andrew,
Yes, these anonymous functions require PHP 5.3. I might consider to restore backward compatibility to PHP 5.2.x doing what you described. Unfortunately, nothing beats the elegance of anonymous functions in that use case 🙂
Are you sure the plugin is activated? Sometimes the activation fails. Please double-check the status in the plugins list.