Dear Folks at Codeless support,
I am wondering if you can help me with this.
I have a bunch of portfolio entries, which I have categorised as events in years as well as decades. So, for example, an event in 1979 would be categorised as being in the 1970s as well as 1979. I further have pages for individual for each decade spanning 1950s to 2010s, with each consisting of portfolio categories making up the years in a particular decade, eg. 1970, 1971, 1972 – 1979.
I have a separate Overall page with a Post Grid (Using VC), where the data source is set to “Pages” and the narrow data source is set to “decades”. Everything worked fine previously, however after the old 1970s decade page (from the above) was deleted and a new page added using the same settings, the new 1970s decade page doesn’t appear in the Overall page (but the others do).
What could be the problem? Can you please help?
The posts are sorted automatically based on their creation date. By deleting and creating again the 1970 page, the page may have changed it’s order. I suggest you check better the overall page, as it could be showing in the last added items.
Can you post some pages of this? So we can understand better the picture.
To custom order the posts, we suggest using a custom plugin such as “Post Type Order“.
You can use it to reorder any custom type post such as portfolio items, posts and codeless slider slides.
I’m not sure how I can share some pages of this with you as the site isn’t live yet. Any suggestions?
We’re pretty much stumped by this. All other pages appear in the Post Grid where narrow data source is used and sorted by Title. We have also just realised that 2000s has gone missing as well.
If we don’t use narrow data source, the missing page (1970s) appears.
Separately, we don’t seem to be able to edit the URL of the 1990s page – which shows up as (/1990s-2)
If you have the site set up in an online server, even if not live yet, you can send us some wp credentials in a private reply. So we can give this a closer look.
If the site is in localhost, then there is no way for us to check it.
I tried rebuild the same situation on my side, but this does not happen. Let us know if you can give us access so we can check the configurations.
This reply has been marked as private.
yes, the private reply is safe enough. Only you and support admin can see the content of a private reply. Or add the credentials in your profile data. The same policy goes for it too. Only you and admins can see them.
Read this article for more information.
You must be logged in to reply to this topic.