by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 2019 21:29

    nitriques on 3.0.x

    Redirect loggued in users to AP… Add documentation about unambig… Allow numeric values in schema … (compare)

  • Jan 29 2019 19:40
    timokleemann commented #2861
  • Jan 28 2019 10:50
    animaux commented #2574
  • Jan 25 2019 18:25
    nitriques commented #2865
  • Jan 25 2019 18:23
    wdebusschere closed #2865
  • Jan 25 2019 18:23
    wdebusschere commented #2865
  • Jan 25 2019 18:09
    nitriques commented #2865
  • Jan 25 2019 18:09
    nitriques commented #2865
  • Jan 25 2019 18:07

    nitriques on 3.0.x

    Avoid double insert (write) exe… (compare)

  • Jan 25 2019 18:07
    nitriques closed #2882
  • Jan 25 2019 18:06
    nitriques milestoned #2882
  • Jan 25 2019 18:06
    nitriques labeled #2882
  • Jan 25 2019 18:06
    nitriques assigned #2882
  • Jan 25 2019 18:06
    nitriques review_requested #2882
  • Jan 24 2019 22:06
    wdebusschere commented #2865
  • Jan 24 2019 21:58
    wdebusschere commented #2865
  • Jan 24 2019 21:10
    nitriques commented #2865
  • Jan 24 2019 20:33
    wdebusschere commented #2865
  • Jan 24 2019 20:33
    wdebusschere commented #2865
  • Jan 24 2019 17:57
    nitriques commented #2865
Alexander Rutz
@animaux
@pixelninja :thumbsup:
Alexander Rutz
@animaux
Argh! Has anyone ever encountered this one?
Entity 'shy' not defined in Entity, line: 159 /www/htdocs/w01a0f68/2020/symphony/lib/toolkit/class.xsltprocess.php:143
Wannes Debusschere
@wdebusschere
@animaux never! :)
do you know where this shy comes from? Search code/db?
Alexander Rutz
@animaux
Apparently there is a ­ in the search excerpts I’m trying to process via XSLT.
I wonder if I can force the search extension into using unicode instead of escaping soft hyphens.
Wannes Debusschere
@wdebusschere
or ignore this special characters
or avoid using ­ :)
Alexander Rutz
@animaux
Would be counter-productive not to use soft hyphens
    private function fixEncoding($in_str) { 
        $cur_encoding = mb_detect_encoding($in_str);
        if($cur_encoding == "UTF-8" && mb_check_encoding($in_str,"UTF-8")) {
            return $in_str; 
        } else {
            return utf8_encode($in_str);
        }
    }
I guess this is the smoking gun.
Wannes Debusschere
@wdebusschere
Alexander Rutz
@animaux
It’s not a problem with the soft hyphen per se. Any other entity would create the same problem.
Nice find in the search_index code: // no idea what this next line actually does, nothing is harmed if it's simply commented out...
The problem is likely somewhere in the parseExcerpt()-function. Which is a complex beast.
Alexander Rutz
@animaux
Ah, sanitize(). (sorry for talking to myself aloud)
Alexander Rutz
@animaux
But I still have no idead at what point the entity is actually created.
Alexander Rutz
@animaux
OK, in case this es helpful to anyone: apparently there were some ­s in my markdown fields that were not translated to Unicode. ¯_(ツ)_/¯
Alexander Rutz
@animaux
Also he bloody excerpt engine creates a stray ampersand! Ha!
Alexander Rutz
@animaux
OK, that was my fault … nevermind me! ;)
Phill
@pixelninja
Hello Symphonists. What methods do you use to preview content before making it live? Not just new content like News that could be published/unpublished, but content that is already live? E.g the homepage has content and images, how do you update the image but preview it before the public can view it? Some kind of content version control?
Alexander Rutz
@animaux
@pixelninja there was a version control extension for symphony once, but it did not provide any means of previewing older versions in frontend rendering. I’d love to have a stable up2date version of that though.
If you have means of previewing unpublished backend content in the frontend, you could create a copy of your content and update only the image. Not sure if that’s what you mean.
Juraj Kapsz
@jurajkapsz
@pixelninja None. As a sidenote, I view this feature in practice as superfluous and all my users go easy along without it. E.g. changing an image is straightforward, selecting one too.
Phill
@pixelninja
Yeah it’s not normally a problem. A client of ours has asked how they can make content changes for sign off before making live, so yes changing an image is easy, not making the change live yet while the page is live doesn’t seem doable.
Phill
@pixelninja
Does anyone know if/how I could trigger fields within the section editor to reorder? I'm injecting fields in and need to update the index of each field after the injected one, but before I start looping over them I thought I'd see if I could just trigger a function within the orderable class or something. I can't see where.
Phill
@pixelninja
nevermind, found it :sunglasses:
Wannes Debusschere
@wdebusschere
Latest realisation with symphony cms
Juraj Kapsz
@jurajkapsz
Really nice @wdebusschere !
Alexander Rutz
@animaux
Leuk!
Wannes Debusschere
@wdebusschere
Thx
cylkee
@cylkee

Hello, all. Has anyone come across this error caused by a right single quote in a field on which a data source is filtering via a Page parameter? Despite that, the handle in the XML doesn't contain and matches the Page parameter. When I swapped it for a normal apostrophe ' all was fine.

Sym 2.7.10, PHP 7.3, MariaDB 5.5

This page could not be rendered due to the following XSLT processing errors:

General:

XSLTProcessor::transformToXml():
    Warning: string contains a character that is out of range! Substituting "?".
    Warning: string contains a character that is out of range! Substituting "?".
    Warning: string contains a character that is out of range! Substituting "?".
cylkee
@cylkee
Baffling. Some entries are okay, some are not. I tried copying a from a working entry in case it could be charset related but no joy.
Alexander Rutz
@animaux
@cylkee I had something similar recently. Are you using the url-encode utility or something alike?
Actually is an apostrophe ;)
Whereas ' is not.
But not in programming obviously. </smartypants>
cylkee
@cylkee
@animaux Ah, yes, thanks. Indeed it is this url-encode utility causing the problem. I guess I should have searched my xsl files for that warning message ;)
Are you continuing to use it, or is there a UTF-8 alternative?
cylkee
@cylkee
I'm curious about this in url-encode: <xsl:message terminate="no"> If terminate is no (default), should it cause Symphony to display an XSLT Processing Error in the front end? (it also adds to Symphony's log).
Alexander Rutz
@animaux
In my case it was sufficient to add the problem-character to the <xsl:variable name="safe">-set.
In the url-encode.xsl utility.
Alexander Rutz
@animaux
@cylkee never noticed the<xsl:message terminate="no">. Did you try different settings? Did my second hint help in your case?
cylkee
@cylkee

@animaux Thanks. I wasn't convinced it's a safe character so I decided to leave url-encode as is and cleanse quotes before passing a string to it. Not going to mess with xsl:message for now.

Actually is an apostrophe ;)
Whereas ' is not.

Looks like it's both https://en.wikipedia.org/wiki/Apostrophe ;)

Alexander Rutz
@animaux
Still, a »typewriters apostrophe« is typografically wrong to use anywhere else than on a typewriter or code. I have to be a pilkunnussija on this! ;)
German Wikipedia is more concise on this issue: https://de.wikipedia.org/wiki/Apostroph#Typografisch_falsch
Peter Skirenko
@petertron
Peter Skirenko
@petertron
The extensions site is ignoring my releases.