Extension access only:
* Cobi Carter (cobi): ClueBot
* Ryan Kaldari (kaldari): Staff developer for fundraising
-- Tim Starling
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, Jun 2, 2010 at 1:42 AM, K. Peachey wrote:
> On Tue, Jun 1, 2010 at 11:22 PM, Marco Schuster
> wrote:
>> On Tue, Jun 1, 2010 at 4:09 AM, Jacopo Corbetta
>> wrote:
>>> In our experience, the biggest obstacle is to get the different
>>> browsers to reliably make the same changes to HTML. Th
On Tue, Jun 1, 2010 at 11:22 PM, Marco Schuster
wrote:
> On Tue, Jun 1, 2010 at 4:09 AM, Jacopo Corbetta
> wrote:
>> In our experience, the biggest obstacle is to get the different
>> browsers to reliably make the same changes to HTML. The editor
>> interface is non-standard, and browsers sometim
"Danese Cooper" wrote in message
news:4c04a2ba.3070...@wikimedia.org...
> Just noting that we at WMF have been talking to Wikia about taking a
> look at their code to see if it can be made useful for WMF properties.
> Expect to hear more about Rich Text Editing soonish.
>
> Danese
What are we e
The error should say the address could not be geocoded. A further issue is
that the geonames parameter and default geoservice for googlemaps are not
working, and Maps is using geonames for everything. You can set this in
localsettings to work with the Google service, which does not fail at
several
Assuming you use Google Maps, the boxes should show a vertical scrollbar
when there is to much content to fit. This has been slightly tweaked in 0.6,
but should still work in 0.5.5.
--
Jeroen De Dauw
* http://blog.bn2vs.com
* http://wiki.bn2vs.com
Don't panic. Don't be evil. 50 72 6F 67 72 61 6D 6
Thanks. In the mean time, v0.5.5 seems to be working ok for me now.
The process installing, removing and reinstalling Vavlidator and Maps
somehow seemed to fixed it.
One more question: How can I enlarge the description box for each item
using Maps? I have long descriptions that run outside the whi
There indeed appears to be an issue on 1.15. I will investigate this, and if
it is really there, will release an update to fix this very soon. Apologies
for the inconvenience :)
--
Jeroen De Dauw
* http://blog.bn2vs.com
* http://wiki.bn2vs.com
Don't panic. Don't be evil. 50 72 6F 67 72 61 6D 6D 69
Thanks, however I've followed those directions to a T. Now with v0.6,
I'm getting no points appearing along with these errors:
-Chris
On Tue, Jun 1, 2010 at 3:29 PM, Jeroen De Dauw wrote:
> You can simply disable the non-geocoding features. See the docs [0] or look
> in the Maps settings file
On 6/1/10 8:24 AM, Roan Kattouw wrote:
> 2010/6/1 Conrad Irwin:
>
>> The other solution is to use a proper MVC framework, and define
>> everything in terms of modifications to the wikitext (and you can then
>> constrain what those modifications are to avoid mangling) and run that
>> through a p
You can simply disable the non-geocoding features. See the docs [0] or look
in the Maps settings file.
The Google Maps extension does not have a separate geocoding parser function
as far as I'm aware.
If you get a warning saying you don't have Validator installed, you do not
have it installed (co
The only reason I'm using the maps extension is for the geocoding. Is
geocoding working with the Google Maps extension?
-Chris
On Tue, Jun 1, 2010 at 2:01 PM, Chris Thomas wrote:
> Using 0.5.5 I still get the "The following addresses could not be
> geocoded and have been omitted from the map". I
Using 0.5.5 I still get the "The following addresses could not be
geocoded and have been omitted from the map". I'm using the format:
{{#display_points:
Address
~Title
~Description
;
Address
~Title
~Description
;
|width=800|height=600|zoom=4|center=41,-91|types=normal|controls=large
}}
Using 0.
On 01.06.2010, 21:15 Chris wrote:
> Ok, I took your advice and upgraded to Mediawiki 1.15.3. I still have
> the same problem.
Which of them, "Call to undefined method Parser::getOutput()" or "The
following addresses ..."?
--
Best regards,
Max Semenik ([[User:MaxSem]])
__
Ok, I took your advice and upgraded to Mediawiki 1.15.3. I still have
the same problem.
-Chris
On Tue, Jun 1, 2010 at 10:36 AM, Jeroen De Dauw wrote:
> Hey,
>
> I suggest you upgrade your MW to the latest release. Maps is build for 1.15
> and 1.16.
>
> Cheers
>
> --
> Jeroen De Dauw
> * http://b
2010/6/1 Conrad Irwin :
> The other solution is to use a proper MVC framework, and define
> everything in terms of modifications to the wikitext (and you can then
> constrain what those modifications are to avoid mangling) and run that
> through a parser to generate the html preview. Alternatively,
On 31 May 2010 23:53, William Le Ferrand wrote:
> Dear all,
>
> I've started to develop a simple wysiwyg editor that could be useful to
> wikipedia. Basically the editor gets the wiki code from wikipedai and builds
> the html on client side. Then you can edit the html code as you can imagine
> and
Hey,
I suggest you upgrade your MW to the latest release. Maps is build for 1.15
and 1.16.
Cheers
--
Jeroen De Dauw
* http://blog.bn2vs.com
* http://wiki.bn2vs.com
Don't panic. Don't be evil. 50 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69
66 65!
--
On 1 June 2010 16:33, Chris Thomas wrote:
I'm running MW 1.12 on Debian Lenny and I installed the Maps 0.5.5
extension. It works, however I get this message for random points when
I refresh. The list of points that aren't geocoded change with each
refresh.
"The following addresses could not be geocoded and have been omitted
from the map"
On 1 June 2010 07:03, Danese Cooper wrote:
> Just noting that we at WMF have been talking to Wikia about taking a
> look at their code to see if it can be made useful for WMF properties.
> Expect to hear more about Rich Text Editing soonish.
:-D :-D
Weeks, months?
- d.
_
On Tue, Jun 1, 2010 at 4:09 AM, Jacopo Corbetta
wrote:
> In our experience, the biggest obstacle is to get the different
> browsers to reliably make the same changes to HTML. The editor
> interface is non-standard, and browsers sometimes disagree on encoding
> rules, escaping, choice of tags, etc.
Yes, I'll definitly keep that in mind. Currently I'm thinking that for
deleted images and old versions of images I'll keep all the metadata
inside img_metadata as serialized php, since most of the use cases for
having metadata in a different table really only apply to the current
version of images.
Hi!
Another approach is to reduce the complexity of wikitext editing by
using syntax highlighting and javascript dialogs. There is wikEd editor
which is being developed with such approach in mind:
http://en.wikipedia.org/wiki/User:Cacycle/wikEd
I does diffs, too.
Dmitriy
bawolff wrote:
>
> However, if I do implement a new table as part of this, it will
> probably use page_ids to identify the image - I don't see any reason
> to artificially restrict it to just the file namespace.
Do remember that we'll also want to store metadata for old versions of
images. And
24 matches
Mail list logo
