I am having a problem that seems to be somewhat common with using pagination on pages other than index.html in a Jekyll project.
I found this post that seemed to be exactly what I am looking for:
Jekyll Pagination on every page
However, the solution does not work for me. According to the documentation on Jekyll's website, the following code in _config.yml should change the paginator to use /Blog/index.html rather than /index.html:
gems: [jekyll-paginate]
paginate: 2
paginate_path: "/blog/page:num/"
I have rebuilt and restarted my local server, but the paginator still only works on the /index.html and not /Blog/index.html.
Does anyone have an idea what I could be missing here?
The paginator internal logic is to :
(from code comment) "Determine if a page is a possible candidate to be a template page. Page's name must be index.html and exist in any of the directories between the site source and paginate_path."
choose the one closest to paginate_path in length.
In your case Blog/index.html is not recognized as existing in /blog/ path, because Blog != blog.
Or you rename your containing folder to blog, or you set paginate_path: "/Blog/page:num/"
Related
as expected, there coming more and more with TYPO3. I'm very in TYPO3 and working with the bootstrap package. Therefore I don't understand loads of stuff.
The task is actually very simple (i guess). I just want to include a search field on in my page with indexed search. I included the extension with the extension manager.
So far so good, the search field is shown and it's able to find content on my page, but when I select one of the search results this page is shown:
Error message
Does anyone understand what happened here?
Many thanks in advance for your hints!
cheers,
expikx
I have already asked this on the LCMS Google Group, but the post got 3 views in a week and I can't continue my project with an entire page missing...
I have been getting an error when trying to push a specific page on wagon 1.5.4 on locomotivehosting and on my own hosting server. Everything works fine on the local wagon serve.
Warning: NOT all the pages were pushed.
Check that the pages inheritance was done right OR that you translated all your pages.
The strange thing is that it works on some pages that are almost identical (see below). My original problem was with the "elektronik-entwicklung" page.
Image: some pages were uploaded, but not all.
What I have tried:
deleted and re-pushed entire website
pushed pages with different slugs and same content, which only worked partially
I tried updating a lot of almost identical pages just with varying names and slugs, only to find out that there was no system behind the choice of which pages got uploaded (e.g. "l-entwicklung.liquid" got pushed, but "a-entwicklung.liquid" didn't get pushed; cf. image on Google Group post).
The files I created to test have the same content, just the corresponding slugs are different. E.g.:
---
title: Elektronik
slug: elektronik-entwicklung
listed: true
published: true
---
{% extends engineering/engineering-subpage %}
Any ideas?
After a lot of pain, I finally decided to upgrade the whole thing to locomotivecms 3.0 and wagon 2.0.
This solved the problem.
I'm using Laravel 4 pagination, and want to remove the page=1 and serve the default string instead; for example:
http://domain.com/search-results/
instead of
http://domain.com/search-results/?page=1
Of course, for page >=2, it's just fine to leave:
http://domain.com/search-results/?page=2
Currently Laravel will always default to showing ?page=1.
Accomplishing what you want (always defaulting to not showing ?page=1) involves a mix of extending/using your own Presenter and/or also by using a custom Pagination view.
Stock pagination views are here, but you can create your own and define it within the view.php config.
In my blog, I do similar. My pagination view is here. You can see it loads in a custom Presenter class.
Note that my blog may not be up to date with latest Laravel code, but that should get you on your way to making the edits you need to do to accomplish that.
You may be able to skip code altogether and use a server configuration to redirect - That link assumes Apache.
I usually find all the answers to my question but this time I could not find any. This if actually the first time I post on stackoverflow!
Here is my problem.
The root of my website: "www.example.com" returns a blank (not empty) page when I use Google Webmaster Tools to fetch my website. When I look at the rendered HTML, it is exactly what it should be, but the preview of the page is just blank.
All the other pages of my website like "www.example.com/sample_page.html" seem to give the proper preview though. I have even tried to make a redirection (htaccess) of the root domain "www.example.com" to "www.example.com/sample_page.html" but it also gives a blank preview.
I use cached HTML files so it does not have anything to do with enabled JS or whatsoever. Furthermore, like I told you, the rendered HTML seems OK it's just the preview that does not return anything.
Any hint is greatly appreciated as I have been trying to find a solution since a few weeks now.
I've made a change to what I thought was the main default template page in a hosted version of Sharepoint 2007, but the search page hasn't picked up the change.
Can someone please either give me a list of all the default page files, or tell me how to identify them? It's really important that I add a JS script call across all pages everywhere on the site.
Thanks!
Point of clarification: for now, I'm just trying to include a jQuery reference. I really don't think I'm trying to do anything complicated or unusual - I just want this include to be be global across all pages by default. I've modified /_catalogs/masterpage/default.master with:
<HEAD runat="server">
<script src="/Global%20Site%20Files/jq1.4.2.js" type="text/javascript"></script>
EDIT
I just did a search of the source code for a statically defined meta-tag and found that the default.master I altered is in fact the only file in the search results!!! This means, as far as I understand, that my jQuery include should have worked! I'm more confused than ever...
Hi What i can see is the way you are refrencing is wrong you should use full Qualified URL for
src attribute in script tag currently you are using relative path that might be a cause of error
Turns out that the issue is not a question of multiple page templates or master files. The search results page (which is the primary page in question) does not use the default.master file. Moreover, even as an administrator, I don't have the ability to edit the search results page.
In the end, it looks as though I was looking for what I thought was a solution, but was really just a red herring. I'm going to repost a more specific question to my problem.