aparsley

Has this been resolved yet? I am having the same issue. I am using 1.76b in IE11. I’ve tried using no dashes in the ID or class. The print window still disappears right when it pops up.

Great. Thanks!

I was wondering about seo. I’m also concerned about “search” capability now, along with a few other issues of doing it this way. Definitely think there is much room for improvement, but a step in a good direction. I look forward to see your future additions! I’d be happy to help beta test.

Sorry to keep stretching the thread, but new things keep clicking in my head ?? I’ve got a fairly clean schematic that does away with creating php files. I’m using standard urls. Not sure if it’s possible to use permalinks at this point anymore. Let me know if you have any ideas to clean this up anymore!

Note: custom post “projects” are no longer indexable.

Starts with a page now – “Projects”
.com/projects/?views=list or ?views=single

[pass global="_GET" field="views"]
 [if pass="{FIELD}" value="list"]
  [content type="view" name="list-project"]
 [/if]
 [if pass="{FIELD}" value="single"]
  [content type="view" name="single-project"]
 [/if]
[/pass]

Then the “views” (custom post) are:
list-project (had to create new urls for links)

[pass global="_GET" fields="tax, term"]
[loop type="project" taxonomy="{TAX}" term="{TERM}"]
          <a href="[url site]/projects?views=single&id=[field id]">[field title]</a>
[/loop]
[/pass]

single-project

[pass global="_GET" field="id"]
[loop type="project" id="{FIELD}"]
[field title]
[/loop]
[/pass]

I have the single-* and list-* specifically stated to “project”, but I guess you can really make these generic views for display any post type.

Got it figured out once I disabled re-writes.

[pass global=”_GET” field=”project-type”]
[loop type=”project” taxonomy=”project-type” term=”{FIELD}” paged=”1″]
[/loop]
[/pass]

.com/?project-type=website

I guess I’m stuck again. Can’t figure out how to utilize this method with category/taxonomies. I’m thinking [pass] will work, just not sure how to implement it.

Currently with the traditional way, I have taxonomy-project-type.php. This basically just queries the projects, except it’s already filter by “project-type” by default. It is using content-projects.php just like archive-projects.php does, except filtered. URL would be site.com/project-type/{type}.

I think I need…
taxonomy-project-type.php
– [content type=”view” name=”tax-project-type” {pass the type from URL}]

view->tax-project-type
– [loop type=”project” taxonomy=”project-type” term={get}]

Thanks for your help!

I decided to use a custom post type (views) instead of pages. Works much cleaner than having a bunch of extra pages. Also this way the “view” cannot be seen/indexed directly. It’s only visible by the standard permalink created by archive-project.php/single-project.php. Nice!

archive-project.php
– [content type=”view” name=”archive-project”]

view->archive-project
– [loop type=”project” …]
– [field title-link]

single-project.php
– [content type=”view” name=”single-project”]

view->single-project
– [field title]
– etc

Awesome. I was mostly thinking just the ability to create front-end forms to submit or edit custom post data. Good luck, I’ll be looking forward to it!

oh, hadn’t thought of that! That’s definitely a step in the right direction.

I’m sure this is a huge task, but is there any hope of someday using CCS for edit/input data to database? Wishful thinking, since you’ve made displaying the data so easy. Thanks again for the great plugin!