Tagged: blog posts, grid, pagination
-
AuthorPosts
-
December 10, 2017 at 12:24 am #887002
Hi,
we use the Blog Posts element in the Avia Layout Builder on our main Page, displaying new Posts in a grid. We have set maximum ‘Post Number’ of 8 posts. When the ‘Pagination’ option is set to ‘yes’ and the user switches to the page 2 to see a grid with older Posts, there’s just a blank page section with no content. Why’s that and what should we do to fix it?
Thanks
December 10, 2017 at 4:56 am #887045Hey jan_mazak,
Please, share with us your WP credentials?
Best regards,
John TorvikDecember 10, 2017 at 9:55 am #887070This reply has been marked as private.December 11, 2017 at 7:03 am #887243Hi,
Thanks for the login details, I get the same problem on my end though I’m not sure why that is happening. Could you try deactivating all plugins to see if one of them is causing a conflict please?
Best regards,
RikardDecember 11, 2017 at 2:58 pm #887435Thanks Rikard. I tried to deactivate all plugins one-by-one with no result on the issue. Then I tried to deactivate all of them at once, but with no result on the described issue as well.
December 12, 2017 at 9:14 am #887790Will you help? Do you know where’s the problem?
December 12, 2017 at 11:19 am #887823Hi jan_mazak,
Yes, we had this before, it was either a plugin conflict, permalinks settings or .htaccess issue.
Can you please try setting a longer php execution time
https://kriesi.at/support/topic/failed-to-load-resource-the-server-responded-with-a-status-of-403-forbidden/#post-798773If you need further assistance please let us know.
Best regards,
VictoriaDecember 13, 2017 at 9:41 am #888245Dear Victoria, thank you for your kind suggestions.
However, when I change the .htaccess file adding any of the lines described, it causes Internal Server Error when reloading our website. Changing the values to 512M and 256M respectively in the default-constants.php only does not have any effect. Where should be the lines placed exactly in the .htaccess file? Our .htaccess file looks like this:# htaccess rules for subdomains and aliases # to create new subdomain, create a folder www/subdom/(subdomain name) # to create web for alias, create a folder www/domains/(whole domain name) # htaccess pravidla pro subdomeny a samostatne weby aliasu # pro vytvoreni subdomeny vytvorte adresar www/subdom/(nazev subdomeny) # pro vytvoreni webu pro alias vytvorte adresar www/domains/(cely domenovy nazev) # dalsi info a priklady: http://kb.wedos.com/r/32/webhosting-htaccess.html RewriteEngine On # cele domeny (aliasy) RewriteCond %{REQUEST_URI} !^domains/ RewriteCond %{REQUEST_URI} !^/domains/ RewriteCond %{HTTP_HOST} ^(www\.)?(.*)$ RewriteCond %{DOCUMENT_ROOT}/domains/%2 -d RewriteRule (.*) domains/%2/$1 [DPI] # subdomeny (s nebo bez www na zacatku) RewriteCond %{REQUEST_URI} !^subdom/ RewriteCond %{REQUEST_URI} !^/subdom/ RewriteCond %{HTTP_HOST} ^(www\.)?(.*)\.([^\.]*)\.([^\.]*)$ RewriteCond %{DOCUMENT_ROOT}/subdom/%2 -d RewriteRule (.*) subdom/%2/$1 [DPI] # aliasy - spravne presmerovani pri chybejicim / RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^domains/[^/]+/(.+[^/])$ /$1/ [R] # subdomeny - spravne presmerovani pri chybejicim / RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^subdom/[^/]+/(.+[^/])$ /$1/ [R] # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress
December 14, 2017 at 9:15 pm #889092Hi,
Not sure if it can be through htaccess as f it is nginx it will not function
Can you please ask your hosting provider? it is the best case.Best regards,
Basilis -
AuthorPosts
- You must be logged in to reply to this topic.