Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Welcome to the CollectiveAccess support forum! Here the developers and community answer questions related to use of the software. Please include the following information in every new issue posted here:

  1. Version of the software that is used, along with browser and version

  2. If the issue pertains to Providence, Pawtucket or both

  3. What steps you’ve taken to try to resolve the issue

  4. Screenshots demonstrating the issue

  5. The relevant sections of your installation profile or configuration including the codes and settings defined for your local elements.


If your question pertains to data import or export, please also include:

  1. Data sample

  2. Your mapping


Answers may be delayed for posts that do not include sufficient information.

Display more than 36 intems in the timeline

Hi!

Is there any way to display mor than 36 items in teh timeline in Pawtucket 2?

Regards
/marcin

Comments

  • Which version are you using? The current version should be able to display up to a couple of hundred items, if I'm not mistaken. More than that bogs down TimelineJS terribly.
  • Hi! Im running 1.7.3..I also get: 

    Warning: A non-numeric value encountered in H:\xampp\htdocs\providance17\pawtucket2\app\controllers\SearchController.php on line 382
    When i try to acces the TimeLine..

    Running on a Windows 2012 server.

    /M
  • Hi!

    Found the parameter that sets the number of displayed
    items in the timeline:
     

    The file browse.conf in the themes/conf folder:

    # --- default number of results per page/ajax load

    defaultHitsPerBlock = 36

    Change this to 

    defaultHitsPerBlock = 100 and it works...

    I will open a separate thread for the SerchControler
    issue

  • You're running PP 7.1? This warning is due to a change in 7.1. There's a fix for it in the development branch, which will be a part of the 1.7.6 release.
  • Yes php 7.1 I Found a workaround but i dont know if it breaks something..

    This is the line
    that fails:

    if (($vn_key_start = $vn_start - 5000) < 0) { $vn_key_start = 0; }

    If I change it to:

     $vn_key_start = 0;


  • If you just initialize $vn_start to a numeric value if it's null you'll be ok.
  • Is the bug only in the SearchController.php or are there more places that have the same warning?


  • That's the only one we've seen so far. More users are starting to use 7.1 now, so we've been focussing testing on it as well.
  • Ok!
    Thank you so much for your help!
Sign In or Register to comment.