Just checked and i can confirm that page gets updated after update jobs are executed. In your particular case it seems like there is a problem with your job-queue ( it is stuck by some reason ).

As quick and rough solution i recommend you to clear database table named 'job' and try again;

03.05.2016 22:15, Rowe, Dolores A пишет:
Update.
So my job queue had 3 jobs in it after I uploaded a gif from it's 
[[File:folder.gif]] link.
At that point I still could not see the image on the page where it's link was.  
Then I
selected Edit of that page, and after saving I COULD see the image instead of 
it's link.

HOWEVER, the same 3 jobs are still in the queue after that ?  Why aren't they 
gone ?
And why aren't they being executed automatically ?  How could they still exist 
now that I
can see the folder.gif image ? Oooohhh, we must be getting really close to my 
issue fix.......??

My wiki is pretty much using the generic 1.26.2 LocalSettings.php, and so the 
cache settings
were default.  We have no external cache mechanism set up.
## Shared memory settings
$wgMainCacheType = CACHE_NONE;
$wgMemCachedServers = array();

thx,
L

G:\wwwroot-tss-wiki-secure\tsgs-catalog\maintenance>php showJobs.php --list

refreshLinks File:Folder.gif table=imagelinks recursive=1 rootJobIsSelf=1 rootJo
bSignature=6678a4af73dcbe6bc426f0d5591f87c6aee25deb rootJobTimestamp=20160503185
544 (id=112,timestamp=20160503185544) status=unclaimed

htmlCacheUpdate File:Folder.gif pages=array(1) rootJobSignature=80acc047983e061d
ba0c3e0c695f00e9e533e2bf rootJobTimestamp=20160503185544 (id=113,timestamp=20160
503185544) status=unclaimed

recentChangesUpdate Special:RecentChanges type=cacheUpdate (id=111,timestamp=201
60503185502) status=unclaimed

------------------------------

Message: 2
Date: Mon, 2 May 2016 17:36:19 +0300
From: Vedmaka <[email protected]>
To: [email protected]
Subject: Re: [MediaWiki-l] MW 1.26.2 issue with image loading
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed

I believe you should also check your cache settings in wiki - there are only 
two reasons exists why you encountering this behavior:

1) You have caches enabled ( either local or external like CloudFlare )
2) You have job queue overfilled with jobs, so new job is not executing after 
you uploaded image. Please try to execute maintenance script 
/maintenance/runJobs.php and see if it will help

02.05.2016 16:05, Rowe, Dolores A пишет:
The $wgJobRunRate is set to 1 (DefaultSettings.php) in v1.26.2 where the image 
is not loading automatically, however it was set to 1 in v1.22.x as well where 
the images are working correctly.



What is yours set to ?  Are you using v1.26.2, and do you see the same problem 
with the image loading ?

thx,

L



Message: 1

Date: Fri, 29 Apr 2016 23:37:37 +0300

From: Vedmaka <[email protected]<mailto:[email protected]>>

To:
[email protected]<mailto:[email protected]
g>

Subject: Re: [MediaWiki-l] MW 1.26.2 issue with image loading

Message-ID:
<[email protected]<mailto:fb305142-dba5-
[email protected]>>

Content-Type: text/plain; charset=utf-8; format=flowed



Check your https://www.mediawiki.org/wiki/Manual:$wgJobRunRate value



25.04.2016 18:51, Rowe, Dolores A пишет:

Dear Teammates,



In MW 1.22.x family, we could edit a page and insert an image link

like [[File:myImage.png]], save the page, upload the image from it's link on 
the saved page, and voila it was there !!



With MW 1.26.2, after the upload, the image is not showing unless we

edit and save the page again.  Is this a bug ?  Or are we missing a setting ?



thanks for any help or suggestions,

Lori


_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l





--

_____________________________________________________________
Mediawiki & Semantic Mediawiki support: https://mediawiki.pro





_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Reply via email to