eZecosystem / Mirror / GG @ GitHub

@gggeek
  • @gggeek a56b8ca
    Add one more test for wrapped php functions: preserve php objects in …
  • @gggeek be406d6
    Add test for the method signature of wrapped functions
  • 3 more commits »
05/23/2015 07:59 pm   Gaetano @ GitHub   Mirror   Link  
@gggeek
05/23/2015 03:41 pm   Gaetano @ GitHub   Mirror   Link  
gggeek commented on pull request ezsystems/apidoc.ez.no#3
@gggeek

well, no-one ever deprecated it. It seems that the sites which are under the responsibility of the Community Board recently are a bit neglected tho…

05/21/2015 04:22 am   Gaetano @ GitHub   Mirror   Link   @3
gggeek commented on pull request ezsystems/ezpublish-legacy#1171
@gggeek

nitpick: cache file

05/20/2015 11:02 am   Gaetano @ GitHub   Mirror   Link   @5
@gggeek
05/17/2015 05:44 pm   Gaetano @ GitHub   Mirror   Link   @6
@gggeek
  • @gggeek cc8f06c
    fix previous commit: leftover debug code in server.php
05/16/2015 08:25 pm   Gaetano @ GitHub   Mirror   Link   @12
@gggeek
  • @gggeek a11cdd0
    Improve generation of methods signature by the Wrapper class
05/16/2015 08:18 pm   Gaetano @ GitHub   Mirror   Link   @8
gggeek commented on pull request ezsystems/ezfind#61
@gggeek

would be nice to have :-) I'd use _lat, _long fpr the names of solr fields storing the separate coordinates instead of 0 and 1 Also, not sure about…

05/15/2015 01:01 pm   Gaetano @ GitHub   Mirror   Link   @8
@gggeek
05/14/2015 07:52 pm   Gaetano @ GitHub   Mirror   Link   @10
gggeek commented on pull request ezsystems/ezpublish-legacy#1167
@gggeek

My 2c: this code seems a bit too complex for the problem at hand - I do not think it warrants adding apis inside the clusterfilehandler (think abou…

05/13/2015 04:58 am   Gaetano @ GitHub   Mirror   Link   @8
@gggeek
05/12/2015 05:56 pm   Gaetano @ GitHub   Mirror   Link   @7
@gggeek
  • @gggeek 92e61c9
    Refactor demo files (client side): remove redundant ones; make sure a…
05/12/2015 05:49 pm   Gaetano @ GitHub   Mirror   Link   @9
gggeek commented on pull request ezsystems/ezpublish-kernel#1247
@gggeek

It's definitely not my responsibility to decide the roadmap for the eZ platform, so take this as mere advice. But imho it would be a bit of a shame…

05/07/2015 08:58 am   Gaetano @ GitHub   Mirror   Link   @15
gggeek commented on pull request ezsystems/ezpublish-kernel#1247
@gggeek

@kore I see your point. Still, it seems that any search engine used to index eZP content ends up having to deal with locations as well as contents …

05/07/2015 04:40 am   Gaetano @ GitHub   Mirror   Link   @12
gggeek commented on pull request ezsystems/ezpublish-kernel#1247
@gggeek

PS: I think that it would be valuable to get more feedback from ezcontentstaging / ezcontentsync (especially the latter) into this specification. d…

05/07/2015 04:21 am   Gaetano @ GitHub   Mirror   Link   @12
gggeek commented on pull request ezsystems/ezpublish-kernel#1247
@gggeek

I think the document should go in greater detail to describe debugging and verification protocols. In my own experience with ezcontentstaging, whic…

05/07/2015 04:10 am   Gaetano @ GitHub   Mirror   Link   @7
gggeek commented on pull request ezsystems/ezpublish-kernel#1247
@gggeek

A problem: with legacy content engine, not all content-editing actions are atomic. E.g. change section of a node or hiding it do affect its childr…

05/07/2015 04:05 am   Gaetano @ GitHub   Mirror   Link   @12
gggeek commented on pull request ezsystems/ezpublish-kernel#1247
@gggeek

The most common usecase would be to seed the target using a copy of the master database. I think this should be mentioned in the spec

05/07/2015 03:59 am   Gaetano @ GitHub   Mirror   Link   @12
gggeek commented on pull request ezsystems/ezpublish-kernel#1247
@gggeek

NB: this means that master should store more or less indefinitely all data that it normally discards. This might pose a storage problem. Eg. versio…

05/07/2015 03:58 am   Gaetano @ GitHub   Mirror   Link   @11
gggeek commented on pull request ezsystems/ezpublish-kernel#1247
@gggeek

TIP: design the system/api to be resilient to edits done on the slave as well. Maybe not as a guarantee that system will work, but this will happen…

05/07/2015 03:53 am   Gaetano @ GitHub   Mirror   Link   @12
gggeek commented on pull request ezsystems/ezpublish-kernel#1247
@gggeek

The big problem with legacy content engine is that a lot of content operations are not atomic. Which makes compaction an hazard. E.g. add content, …

05/07/2015 03:51 am   Gaetano @ GitHub   Mirror   Link   @18
gggeek commented on pull request ezsystems/ezpublish-kernel#1247
@gggeek

Tip: ALL updates MUST be idempotent. This makes the protocol much more stable, reliable, easy to implement. Ideally you would have a log somewhere …

05/07/2015 03:49 am   Gaetano @ GitHub   Mirror   Link   @10
gggeek commented on pull request ezsystems/ezpublish-kernel#1249
@gggeek

@crevillo you probably should add per-language as well :-) (or is the choice of language dictated by http headers in the request? not sure I'd go t…

05/07/2015 03:44 am   Gaetano @ GitHub   Mirror   Link   @14
@gggeek
05/06/2015 05:38 pm   Gaetano @ GitHub   Mirror   Link   @15
@gggeek
plugin makes editor unberably slow
04/29/2015 11:54 am   Gaetano @ GitHub   Mirror   Link   @21
@gggeek
  • @gggeek 99530b7
    set code highlighting in snippets
04/28/2015 06:47 pm   Gaetano @ GitHub   Mirror   Link   @23
@gggeek
04/28/2015 06:30 pm   Gaetano @ GitHub   Mirror   Link   @23
@gggeek
04/28/2015 06:20 pm   Gaetano @ GitHub   Mirror   Link   @19
@gggeek
poor handling of funcsynopsis element and friends
04/27/2015 06:47 pm   Gaetano @ GitHub   Mirror   Link   @21