Ce fil est résolu. Voici une description du problème et la solution proposée.
Problem:
Since View 1.11 default HTMl is wrapped around the View's Loop and this makes it impossible to populate things like charts or other 3rd Party Plugins with Views generated data.
Solution (include the steps to folow here):
At your own risk you can use this Custom Filter:
add_filter( 'wpv_filter_wpv_view_shortcode_output', 'prefix_clean_view_output', 5, 2 );
function prefix_clean_view_output( $out, $id ) {
if ( $id == '375' ) {
$start = strpos( $out, '<!-- wpv-loop-start -->' );
if (
$start !== false
&& strrpos( $out, '<!-- wpv-loop-end -->', $start ) !== false
) {
$start = $start + strlen( '<!-- wpv-loop-start -->' );
$out = substr( $out , $start );
$end = strrpos( $out, '<!-- wpv-loop-end -->' );
$out = substr( $out, 0, $end );
}
}
return $out;
}This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | - | 14:00 – 20:00 | 14:00 – 20:00 | 14:00 – 20:00 | 14:00 – 20:00 | 14:00 – 20:00 |
| - | - | - | - | - | - | - |
Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)
This topic contains 36 réponses, has 2 voix.
Last updated by Steve Il y a 8 années et 5 mois.
Assisted by: Beda.
I need to correct myself.
I am not anymore able to reproduce that Default HTML.
It seems the update solved it.
Please see the screenshot, there is no HTM wrapped around the View anymore.
Correct?
I now get a Chart using your View in the ShortCode.
But, it seems to me it's not correct.
I assume now it's a question of outputting the values in a way the Plugin can read it.
As far I see, Views is now correctly outputting a blank loop, and data is transferred to your ShortCode
Can you confirm this?
dear bead.
it's unfortunately NOT correct.
see enclose my source view of your testing page.
i have transferred your attempt to the live site and got the same results. still div and p.
though i must say i would have loved that the noautop would have done the trick!
i think i will go for noautop as next username … 😉
best,
s
POOOH GUYS!
thanks beda for your input today. and i am sorry your array WAS correct! what i didn't see was that you had created a test view which i had to place in the test post before …
… anyway i stumbled upon it and that's what made me really think:
1.) of course what the h*beeep* is the difference between those two?
to keep this maximum short i am still not aware that everything is under my control but i was able to reproduce the wanted output.
2.) as you can guess: i was also able to transfer it to other views.
3.) in between i found out that views uses an internal cache!!! since when is that? and is it documented anywhere (in plublic)? and of course, beda, you might have been right that also your output was irritated by that cache.
after those first 3 steps: PLEASE MAKE CACHING TURNED OFF AS EASY AS POSSIBLE!!!!!
the option to add cached="off" is WAY NOT ENOUGH!
some mysteries later i had the complete output that i have been looking for. (see screenshot 2, the white one without graph)
as in the very beginning of this thread i turned on the wp_charts shortcode and ended one more time in an empty graph but with quite a bit output below. (see screenshot 1, the white one with the graph)
again one step back an diving deeper into the source code i found that views is outputing just a little space between the quote before and first output value. you can see that pretty clearly in the blue screenshot before wp_charts after datasets=" and labels=". the inner values do not have the same problem as there is no quote before, so the output is straight.
why is that?
how can i get rid of that?
and maybe a bit to early for that argumentation here: how can i make views outputting my values first before processing the whole shortcode?
best,
s
A solution is there, but it's a Custom Code Solution.
Let me first explain what happened, and what will happen in future:
Firstly, a View is not intended to provide DATA to USE, but to DISPLAY it.
(USE of data is the purpose of an API function.)
We have also many new features with the new View.
Like endless scroll, etc.
Also, many future features required us to actually wrap the Views Loop into default HTML -
This being said, we changed how Views Loops are outputted.
This in order for new features to work properly.
This will not change in future.
We need those wrappers as example if you have pagination. It is also needed if you use parametric search. And it will also be mandtory when we add custom frontend sorting controls (future).
So we would need to detect this on a per View basis, counting on settings stored within the View and also some shortcodes that could appear everywhere, even on Content Templates that we can not scan.
I assume you see the complexity of the scans that would be needed to make, in order to dynamically enable or disable Default HTML wrapping.
But now to the solution, I just tested it.
1. Download and install the new Views 1.11
2. Construct a View that displays all results, query some post, output (for now) one post only
3. The View Loop holds as less data as possible.
My test View, copy and paste exactly as is:
[wpv-layout-start] [wpv-items-found] <!-- wpv-loop-start --><wpv-loop>[wpv-noautop]1,2,3,4,5[/wpv-noautop]</wpv-loop><!-- wpv-loop-end --> [/wpv-items-found] [wpv-no-items-found] <strong>[wpml-string context="wpv-views"]No items found[/wpml-string]</strong> [/wpv-no-items-found] [wpv-layout-end]
4. Get your Views ID (URL of Edit View Page)
5. Put this to your functions.php and change the ID:
add_filter( 'wpv_filter_wpv_view_shortcode_output', 'prefix_clean_view_output', 5, 2 );
function prefix_clean_view_output( $out, $id ) {
if ( $id == 'ID' ) {
$start = strpos( $out, '<!-- wpv-loop-start -->' );
if (
$start !== false
&& strrpos( $out, '<!-- wpv-loop-end -->', $start ) !== false
) {
$start = $start + strlen( '<!-- wpv-loop-start -->' );
$out = substr( $out , $start );
$end = strrpos( $out, '<!-- wpv-loop-end -->' );
$out = substr( $out, 0, $end );
}
}
return $out;
}
6. In a page, use the view in this (your plugins) shortcode:
[wp_charts title="linechart" type="line" align="alignright" margin="5px 20px" datasets="[wpv-view name='raw'] next 1,2,3,4" labels="one,two,three,four" scaleoverride="true" scalesteps="5" scalestepwidth="10" scalestartvalue="0"] // of course, you can also replace the numbers after "next" with the view
This actually displays what you see in my screenshot.
Notice that, with this applied to a given View ID:
- Pagination, specially AJAX pagination, will not work.
- Parametric search, specially AJAXed parametric search, will not work.
- Other future features will not work either.
I explained the "why's" above.
Views was (and is) not intended as a Data Provider, but a Data Display engine.
With all new features, and features to come, this default HTML will now be attached all the times to a Views Loop, unless you use above workarounds and approaches.
I hope you can now proceed with your project.
Thank you very much for your patience.
