>
> I am currently on most recent releases of both token and entity and get
> memory errors almost any place tokens are used. There are lots of error
> reports having this problem, and it seems to be release dependent, some
> pairings may work but not the most recent ones. Some of the suggestions are
> to just disable entity (aka Entity API). But it is required by rules and
> rules is required by commerce which I need on my site. I am in the process
> of upgrading from D6 to D7.
>
> The problem sounds like it is caused by entity when it tries to generate
> huge numbers of tokens. I have lots of fields, content types, users, user
> profile fields, etc.
>
> It appears that the developers have given up on the problem, see
> http://drupal.org/node/1272570 but perhaps I just haven't found the
> right answer yet. Has anyone else had this problem and found a solution?
>
> --
> Walt Daniels
>
What's your favorite method to post to S3 via Drupal [D7]?
--
Cheers and rock n' roll!
Jason A. Nunnelley
http://about.me/imjasonn <= social connect info for me everywhere!
Patient Zero, CEM, Member, dosIQ, L.L.C.
Chief Technologist, Member, Tekany, LLC
V.P. Communications, SSGT Defensive Tactics, Inc.
Alahbakash left a message for you
Only you can see the sender and content of your message, and you can delete it anytime. You can instantly reply using our message exchange system:
http://eu1.badoo.com/allahbakash/in/VeH38jUW36Y/?lang_id=3&m=21&mid=4fd1cd6…
If the link in this message does not work, try copying and pasting it into your browser.
This email is part of our delivery procedure for the message sent by Alahbakash. If you have received this email by mistake, please ignore it. The message will be deleted soon.
Have fun!
The Badoo Team
You have received this email from Badoo Trading Limited (postal address below).
http://eu1.badoo.com/impersonation.phtml?lang_id=3&mail_code=21&email=devel…
Badoo Trading Limited is a limited company registered in England and Wales
under CRN 7540255 with its registered office at 12 Red Lion Square, London, WC1R 4QD.
I've been working on a multilingual site and the fact that URL aliases are
selectively available based on language seems a little awkward. I like that
the path module is language aware and stores a language, however I view as
as more of a language provider, than translatable content.
I wrote up some of my thoughts at
http://darrelopry.com/story/using-url-aliasespaths-language-detection-drupa…
I was hoping to solicit some feedback here since I've been away from Drupal
development before posting a patch or creating an issue.
Context: CMI, D8MI, Entity, Framework sprint in Barcelona in 2 weeks.
Background:
- New configuration system for D8: http://drupal.org/node/1270608
- How to make config multilingual: http://drupal.org/node/1448330
- Multiple possible approaches. Uncertainty. Indecision.
- There's been a conf call to discuss and we've agreed on the most
simple variant in order to make progress. To be publicly announced
and summarized as a blog post on Drupal Planet very soon.
-- 'nuff context --
Am 01.06.2012 18:51, schrieb Gábor Hojtsy:
> Just to summarize the situation, currently Jose is the only one
> working on a solution which is based on a more general config realms
> concept and runtime overrides (as per his explanation in the meeting).
> It is not based on the path we decided on at the meeting. Sun and chx
> are busy with other things and the site information patch that Sun set
> as a pre-requisite to start working on the multilingual support patch
> is not yet close to being committed.
1) Meta data about configuration != configuration realms/domains/overrides
The only existing issue that is remotely related is
http://drupal.org/node/1498270 (which I've just moved into the core
queue), but that is about meta data only and should remain about meta
data only.
As soon as a dedicated issue for configuration realms/domains/overrides
exists, I'll post my stack of objections there. ;)
2) I can't speak for chx. But I'm focusing on the config system, almost
exclusively. My promise to whip up a patch to make the site name
multilingual as soon as the site info variables have been converted
still stands. Ideally (long) before Barcelona. Created a placeholder
for that: http://drupal.org/node/1613350
3) Converting site info variables into config
(http://drupal.org/node/1496542) is still artificially blocked on the
issue about guidelines for how to convert stuff
(http://drupal.org/node/1599554) Artificial, because i) the guidelines
never intended to set up a "standard" in the first place, ii) no
objections to the main conversion guidelines at all yet, iii) changes in
direction can still be adjusted later, and iv) it's all about sanity
only and the site info conversion patch only makes sense. I don't see
why these "blockers" couldn't be resolved by tomorrow.
4) In the end, the prototype patch for multilingual config will be
fundamentally different to (1b) configuration realms/overrides.
Meanwhile, these two topics are entirely different beasts for me.
Anyone else is more than welcome to join the party. These changes will
affect each and everything throughout Drupal (8).
--
sun
