Support » Plugin: Page-list » nice, but

  • I don’t like the idea, that your plugin adds a new css file to all of my headers, no matter if I use pagelist on that page or not. for me i only used pagelist on one of about 100 pages. could’n you just use existing classes? or have an optional inline style sheet?

    An other thing is to have more consistent naming. sometimes it is called pagelist, sometimes it is called sitemap.

    otherwise it functions great. thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author webvitalii

    (@webvitaly)

    Thank you very much for your feedback.

    About css file: the file is very small and it is loaded only first time. All next times browser will use the cached copy of the file.
    But inline css is pretty interesting idea and I will think about it.

    About “sitemap” and naming: first version of the plugin was made to show only sitemap of the site. Then the plugin was extended to show different list of pages (subpages, siblings, extended list of pages with images, added different params to shortcodes and so on). But the plugin is having some legacy code and naming from old versions to keep working and not brake (where it is possible) the older shortcodes.

    Hi there,
    thanks for your answer.
    yes I know it is just a a small file – but each plugin adds some stuff, which just adds up. In my view a website should be slim and fast.

    You might find a way to selectively include the css in the header – only if pagelist is used.

    I just noted the naming issue s I was looking for pagelist files and couldn’t find them.

    cheers

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘nice, but’ is closed to new replies.