Reputation
274
Next privilege 300 Rep.
Create new tags
Badges
1 11
Newest
 Yearling
Impact
~6k people reached

  • 0 posts edited
  • 0 helpful flags
  • 21 votes cast
Dec
29
revised how to get archive urls with same origin for custom types and terms?
added 225 characters in body
Dec
29
accepted Does it still make sense using json endpoint ep_mask now that there's the new rest api?
Dec
29
asked Does it still make sense using json endpoint ep_mask now that there's the new rest api?
Dec
29
comment How to pass posts_per_page and paged params query vars to custom taxonomy archive urls?
ok, it suddenly started to work.. Don't know... getting mad.
Dec
29
revised How to pass posts_per_page and paged params query vars to custom taxonomy archive urls?
edited tags
Dec
29
comment How to pass posts_per_page and paged params query vars to custom taxonomy archive urls?
Update: I found out in fact it goes to a 404, and the $post error was correct since I had called the_content() inside the 404 template. Still I can't figure out WHY it ends up on a 404 as soon as I add a paged variable.
Dec
29
comment How to pass posts_per_page and paged params query vars to custom taxonomy archive urls?
Since I'm currently speaking of custom taxonomies, I cannot use the default theme. I'm using mine (I don't use thirdy parts things), but it's really bare bones for now. Permalinks are temporarily off, but I had same results even with perma-on. Basically, when adding paged=2, the dispatcher will route to a wrong template and will not populate variables. The error is coming out of post-template.php, searching for $post->post_content, but $post is NULL, hence the non-object error. It should be an archive, though.. Just like it currently IS without the paged var.
Dec
28
comment How to pass posts_per_page and paged params query vars to custom taxonomy archive urls?
+1 for the posts_per_page being private :), I didn't notice. Anyway, as you wrote, paged is public so should't I be able to pass it on the url? es &paged=2? It currently doesn't work (and yes, I created enough posts for 3+ pages).
Dec
28
comment How to pass posts_per_page and paged params query vars to custom taxonomy archive urls?
To try, I'm just adding to the browser. But what's the point with my question? The problem is the results, not where you write the query. I guess. Thank you.
Dec
28
asked How to pass posts_per_page and paged params query vars to custom taxonomy archive urls?
Dec
21
comment How to correctly translate custom posts url rewrites?
mmm, interesting. So do you mean i should force flush every time the user changes language? Another problem I have, is polylang plugin generating links to products archive > when you're in the product archive page, the language switcher will only change the lang suffix, so ending in smthg like /fr/products, it/products, instead of fr/produits and so on. I guess flushing the rules on lang chnage would not work for polylang, since it has to generate all the links in all languages for the lang menu.
Dec
21
comment Theme localization of “slugs” (custom post types, taxonomies)
urls must speak. So if the slug is (as often) the name of the entity or the taxonomy, the rewriting must take into account plurals as well as translations. That's not an option, both for SEO and simply good practice towards the end users.
Dec
21
asked How to correctly translate custom posts url rewrites?
Dec
18
revised how to get archive urls with same origin for custom types and terms?
added 286 characters in body
Dec
18
revised how to get archive urls with same origin for custom types and terms?
added 8 characters in body
Dec
18
answered how to get archive urls with same origin for custom types and terms?
Dec
18
asked how to get archive urls with same origin for custom types and terms?
Dec
17
accepted how to authenticate for the REST API from a plugin and from command line
Dec
17
comment how to authenticate for the REST API from a plugin and from command line
:) ok, now it's clear! Thank you!
Dec
17
comment how to authenticate for the REST API from a plugin and from command line
@Mark Kauplin: simply, how to retrieve a list of posts from a plugin or from the command line (curl) via the (now with v4.4) native rest api?