Responsible Page no: F22
Explanation |
Video and Pics |
Feed CompletenessNot all Posts on Zerohedge for Austrian and Macro Too many postsDespite the fact that we run 3 crons, FeedWP is not able to load all Zerohedge posts. |
FeedWP uses too high CPU during the write process to the DB. Server gets to the limit.Possibilities:More CPU, but Zerohedge might send more posts. |
|
RSS gives only 20-25 posts per read request.
|
Run Cron only for Zerohedge every thirty minutes. or limit Zerohedge to certain keywords. |
Overtaking: Cron jobs can overtake eachother? |
|
|
DB as bottleneck. |
|
|
Issue: Not reloading posts via CRON from one week The problem was that we migrate two of our blogs on SSL server protocol. But we forgot to migrate their cron jobs on SSL, too. The issue is caused that we update the feed via not-ssl connection. Now we changed the connection. This is made by VestaCP link. It can be changed via CRON Menu. Then edit the two cron jobs and change the link in command field. |
 |
Graphs Imported No PostsExplaining how to use Quick media edit for checking for grahps, which are imported, but not attached to post. You need to check if the not attached image is featured image. You need to check in the original source.
problem The problem is fixed. |
|
Ecoblogs problems Formatting and ControlThis is a quick video for it.snbchf about problem in formatting of the doc page. We should work on Author table, because we have stupid things in it.
problem This issues are fixed. |
|
Create Checklists for CSS IssuesThis video is about checklists and how we need to create checklists for different issues. In this video is showing how to make a checklist of css issues from Acting man feed.
|
|
Performance issuesFor Google (SEO) and for the user (Low bounce rate) is important to visit a site, which is fast enough (no more than 3s. for load). We make tests on every biweekly report with different tools like zoompf, pingdom, webpagespeed and etc. If there is problem, we document it. And after that we work on problem. |
 Bi-weekly: Performance issue from ZoomPF
|
Split into Text and Imagessometimes we are missing images or text of posts. Cron job did not finish. Improvement: Split text and images.See improvement page. |
|
Customer CronsONYX Cron issuesCrons were not running and the site was not loading posts.
The problem was a server issue and by default, the crons were not working. What was the server issue? The server issue was that the crons needs PHP 5.6 to be run smoothly. The problem was that all new blogs by default start using PHP 7, which does not run the crons and it gives an error. So we changed the default behaviour of the server for the crons in the future.
In addition, we had to enable different PHP process only for the crons. Which are the PHP processes for the Crons? Crons are run by server-side processes, different from WordPress itself.
|
See more for