Issues Using Sortable Portfolio

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #527
    Anonymous
    Guest

    Hello,

    I have a couple of questions/issues using the sortable portfolio functions in the Contango Pro Theme. I apologize for writing such a long post but I wanted to provide all the steps to replicate the issues:

    Scenario #1

    1. View Demo for Contango Pro Theme
    2. Choose Portfolio > Sortable Layout > Sortable 2 Columns (you can select 3 or 4 columns as well – does not matter which one)
    3. Sort portfolio by any of the taxonomies listed (e.g. ‘Creative’)

    Issue 1 – it will only sort portfolios on that page and not include results from remaining pages; if I navigate to another page prior to sorting, it has the same behavior on that page as well

    Issue 2 – there is still a page navigation after sorting portfolio; if I navigate to the next page, all portfolios are displayed (just as if I selected ‘All’ and cleared my previous taxonomy selection)

    Observation – it seems that using sort portfolio will filter contents on each page without displaying them all together on one page or as few as possible; and navigating to next page clears the taxonomy selection (this should not happen)

    Question – is this just a glitch with the demo? Or is this a defect within the theme itself? I’m still setting up my website/blog, but haven’t created enough portfolios as test data to verify this for myself

    Scenario #2

    1. Create/publish 4 new portfolios (e.g. portfolio IDs are 1,2,3,4)
    2. Create/save 2 custom sidebars, giving each a different name (e.g. Dog and Cat)
    3. Create 2 new pages, giving each a corresponding title (e.g. Dog and Cat)

    a. Choose Template = Portfolio Sortable 4 Column Template for both
    b. Use Custom Sidebar = Yes for both, choose appropriate sidebar for each page (e.g. Dog and Cat)
    c. Save changes

    4. Go to Appearance > Widgets > Contango Portfolio (Sortable)

    a. Title = Dog
    b. Type = Custom
    c. Client IDs = 1,2 (these are actually portfolio IDs–not client IDs; this briefly confused me into thinking I had to create clients to use this widget–and any other widgets using that field label)
    d. Number of Clients to Display = 2
    e. Layout = Four Columns
    f. Assign widget to corresponding sidebar (e.g. Dog)
    g. Save changes

    5. Repeat steps 4a thru 4g to create/assign widget to other page (e.g. Cat)

    However in step 4c, assign Client IDs = 3,4 (instead of 1,2)

    6. Publish both pages

    Issue – go to the site and notice that all 4 portfolios are displaying in both pages; I would expect each page to display 2 different portfolios (since each widget is set to custom and has different IDs assigned)

    Question – is this a defect? Or am I misunderstanding how this is designed to work?

    Thanks very much for your help and support on this forum!

    Jim

    #1364
    admin
    Participant

    Hello,

    Thanks a lot for your time and explaining your question in a detailed manner.

    Answer of Scenario #1

    Your observation is correct. According to current logic, filtering is possible on the current active results. There are several reasons behind this logic, so it is currently not possible to remember the filtering for pagination.

    Answer of Scenario #2

    You are confusing one step only i.e. 3(a)

    Wrong:

    Choose Template = Portfolio Sortable 4 Column Template for both

    It should be:

    Choose Template = Full Width Widgetized Template

    Logic Behind

    As you are expecting to use widgets, so it should be Widgetized Template instead of any other template. Full Width Widgetized Template is also a powerful feature of Contango Pro. You can design multiple layouts by assigning different widgets to this template.

    Thanks

    #1365
    Anonymous
    Guest

    With regard to Scenario 1…would you consider changing that logic in an upcoming release? It seems the function of filtering data is more useful when there is a larger volume of it for the user to navigate (not when confined to a limited number of records on one page). Please let me know if this is feasible.

    With regard to Scenario 2 – thanks for clarifying. I need to continue to test and explore in order to learn more about how this works.

    Thanks very much for the reply. And please let me know your thoughts about making a change in behavior for Scenario 1.

    Jim

    #1366
    admin
    Participant

    Hello Jim,

    Quote:
    With regard to Scenario 1…would you consider changing that logic in an upcoming release?

    I have forward this request to our developers who are currently working on Update Track of our all WordPress themes for WordPress 4.0. Let see, if they are able to push this change in the current release or not.

    Thanks

    #1367
    Anonymous
    Guest

    Thanks very much for looking into this – please let me know what you find out.

    #1368
    Anonymous
    Guest

    Hello – just checking in…do you have any updates on this issue?

    Thanks

    Jim

    #1369
    admin
    Participant

    Hello Jim,
    We were waiting the release of WordPress 4.0, which is pushed yesterday.
    Now, we are going to push the updates of our themes to ensure the compatibility with WordPress 4.0
    Your suggestion is already in track, and i may wish to include this feature in the release.
    Thanks

    #1370
    Anonymous
    Guest

    Thanks very much!

    #1371
    admin
    Participant

    Hello Jim,

    Quote:
    Hello – just checking in…do you have any updates on this issue?

    You will be happy to hear that Contango is Updated to 5.1 and your requested feature is addressed with many others by our developers in this release. Please see the following thread for details,

    http://designorbital.com/community/threads/wordpress-4-0-and-designorbital-themes.233/

    Thanks

    #1372
    Anonymous
    Guest

    That’s great news! Thank you so much for considering my request and all the support provided on this forum.

    Jim

Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.