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
Moritz Profitlich
@mprofitl
I’ll be happy to compose some
Juraj Kapsz
@jurajkapsz
Juraj Kapsz
@jurajkapsz
That's all :o)
Juraj Kapsz
@jurajkapsz
Juraj Kapsz
@jurajkapsz
Guys, I have further updated the JIT webp version to generate webps on the fly when requested, it goes like this: /image/jit-recipe/filepath/photo.jpg.webp, so you just add .webp at the end of existing JIT requests, everything else stays the same. JIT will then create a webp from the file "/image/jit-recipe/filepath/photo.jpg".
Any good?
It's just a proof of concept for now, did not pushed it to the repo yet. But it works. Haven't tested it yet with caching disabled and you need to use a mode, even if it is a direct display, to get a webp file.
What I don't like about this approach - but that goes for JIT in general - is that you don't get file sizes with JIT-generated images into your XML/presentation to inform user about the file size, if such information is appropriate or legit.
Alexander Rutz
@animaux
@jurajkapsz nice!
Juraj Kapsz
@jurajkapsz
@animaux have polished it, will share in couple of days
@animaux Hope you don't use external images too much, 'cause as of now they are not supported in WebP generation.
Phill
@pixelninja
Out of curiosity, have any of you tried TwicPics before? Combined with my Media Library extension, I have found it a great way to deliver optimised images for each device on the fly. Client uploads full res image to Symphony, TwicPics handles the rest and it's free up to 3gb bandwidth per month.
Juraj Kapsz
@jurajkapsz
@pixelninja not yet, but it sounds interesting. As of now I use JIT for responsive images.
Juraj Kapsz
@jurajkapsz
Guys, I'd like to think I have resolved symphonists/multiuploadfield#39 (multiuploads by click), and there is still a pending PR symphonists/multiuploadfield#38 (SVG file upload fix). I would like to be "39" on top of "38", but maybe I want to make the 38 PR more cleaner (e.g. slovak translation should not be a part of the svg fix branch), so I'm thinking of pulling the PR 38 down and redo it. Also I think it makes sense to create new versions along these updates, e.g. 1.6.3 for svg feature, 1.6.4 for click uploading. What's the best approach of doing so? Should I release my own fork, merging everything into the master? But I also want to contribute to the community releases.
Alexander Rutz
@animaux
@jurajkapsz The Symphonists account is not active anymore. You are best off releasing your own fork, I think.
@pixelninja Even it that sounds handy – don’t like dependencies on third parties, even if it’s »free«.
Phill
@pixelninja
@animaux fair enough! I don't tend to either, so I modified my code to easily switch between TwicPics and internally hosted images just in case. So far it's been a massive performance boost with 0 issues. I would liken it to using Cloudflare.
Alexander Rutz
@animaux
@pixelninja sounds very reasonable. I’m glad I never had to work on sites with huge traffic ;)
Stuart Palmer
@stuartgpalmer
Hi All. I need to use the Search Index extension on a site running 2.7.10. Before I install the standard Symphonists master branch, have any of you got new funky branches that I should consider instead?
cylkee
@cylkee
@stuartgpalmer Check out my PRs https://github.com/symphonists/search_index/pulls I had to make these changes to get it working on Sym 2.7 and PHP 7.3. Sadly, no one appears to be around/able to merge them.
Stuart Palmer
@stuartgpalmer
@cylkee THANKS!
Juraj Kapsz
@jurajkapsz
JIT version with option to generate WebP: https://github.com/jurajkapsz/jit_image_manipulation/tree/webp I've added more info in the readme. Please test it first before putting into production. You also need to prepare a proper html code for presenting webp images with a fallback (source image for that webp, that is either jpg or png). I am thinking of using picture element, I don't have a live example as of now, only tested the recipes.
Juraj Kapsz
@jurajkapsz
Guys, anyone into web accessibility? In a recent related course I got a green on practices mentioned in https://css-tricks.com/use-target_blank/ .
Wannes Debusschere
@wdebusschere
Anybody else getting a warning about get_magic_quotes_gpc()?
Deprecated: Function get_magic_quotes_gpc() is deprecated
cylkee
@cylkee
No, but I'm using PHP 7.3. Deprecated as of 7.4 https://www.php.net/manual/en/function.get-magic-quotes-gpc
cylkee
@cylkee
7.3 which, alas, only receives security support until 6 Dec 2021 https://www.php.net/supported-versions.php at which point I believe will then render the latest 'official' release of Symphony (2.7.10) dead :cry:
cylkee
@cylkee
Irony - https://www.getsymphony.com/ Error 522 Connection timed out. Anyone else have access to the website server and Github repo besides @nitriques? @brendo?
Juraj Kapsz
@jurajkapsz

Anybody else getting a warning about get_magic_quotes_gpc()?

I don't get this warning, looked at a PHP 7.4 site.

Wannes Debusschere
@wdebusschere
it only happens when you have 'error_reporting_all' => 'yes', in the config.php
Juraj Kapsz
@jurajkapsz

it only happens when you have 'error_reporting_all' => 'yes', in the config.php

ok. @cylkee the get_magic_quotes_gpc is non-essential to SCMS, easy transition to PHP 8 in this regard, actually petertron's ready for PHP 8 SCMS 3 already has that solved.

Wannes Debusschere
@wdebusschere
Thanks for this
We are still building all our sites with symphonycms connected to a headless cms
Works really well
Juraj Kapsz
@jurajkapsz
Great, I also use symphony actively, I aim to have a running SCMS 3 website and would like to create some extensions too.
Phill
@pixelninja
I actively use it too but honestly it's getting harder to justify with the lack of support and community :( @wdebusschere what headless CMS do you use?
And does anyone use @pointybeard 's Extended fork?
Wannes Debusschere
@wdebusschere
@pixelninja We developed our own headless cms with Laravel, which has a good medialibrary and allows to create sections,... The frontend is symphony with 0 extensions and 2 remote datasources + caching. This works really well. If anyone is interested, Pm and i give a demo :)
Alexander Rutz
@animaux

I actively use it too but honestly it's getting harder to justify with the lack of support and community :( @wdebusschere what headless CMS do you use?

Same here!

cylkee
@cylkee
Glad to hear there are still devs and users, I did not doubt that. However, without a maintained 'official' repository and a website that is reliable, not to mention mobile-responsive, Symphony CMS will fail to attract new developers, and some may float away, so I fear a slow decline. I will probably continue to use SCMS in a personal capacity, but like @pixelninja, I find it really hard to justify starting a project for a client with software that's headed in that direction. I have done my best to contribute, submitting detailed issue reports and making some basic PRs here and there. PHP is not my strength. I started to test 3.0.0 but lost motivation because there was no activity in the official repo. My strength is front-end HTML/CSS and I could contribute by converting https://www.getsymphony.com/ to be mobile-responsive. But, again, motivation is waning. And how or who would apply new templates to it anyway?
Wannes Debusschere
@wdebusschere
Let's ask @nitriques what is the plan of 288 with symphony?
cylkee
@cylkee
Given lack of response to various @ s, I think he's still having problems with Gitter notifications https://gitter.im/symphonycms/symphony-2?at=5fc9b87c5be1fb21c5f9e45f
Wannes Debusschere
@wdebusschere
We could mail him
cylkee
@cylkee
If someone can PM his direct email address I will invite him to address the community.
Wannes Debusschere
@wdebusschere
@cylkee check PM
cylkee
@cylkee
Thanks, I'll send him a message
Juraj Kapsz
@jurajkapsz

And does anyone use @pointybeard 's Extended fork?

@pixelninja haven't tried it yet, thought it is mainly about bringing XSLT 3 to SCMS but it looks like it has more improvements and has more recent updates. Looks interesting, will check it further later on.

Juraj Kapsz
@jurajkapsz

I actively use it too but honestly it's getting harder to justify with the lack of support and community :( @wdebusschere what headless CMS do you use?

I agree. Also about what @cylkee wrote, I want to further elaborate on that, but my recent idea was to create a common SCMS rolling edition ("RE"), which would contain regular updates and improvements on the go. Very much like you have linux distros, there are LTS versions which is the current SCMS, and then rolling distros or in-between LTS releases. And anything good from RE could be potentially taken into the next official SCMS LTS release, should that later on happen. Anyway, it's a fresh idea, I'm still in the dark about versioning RE etc. I would not even mind to dump PHP 7 compatibility in RE in favor of PHP 8 / not having redundant code for older PHP versions.

Alexander Rutz
@animaux
@nitriques introduced LTS for the 2.7.x version, but that did not go very long. For my part I’d love to see a stable 2.7.x version with all the necessary fixes. 2.7.10 has some nasty bugs and I have a local copy with some hot fixes, but that’s not a very nice state to have symphony in. Personally I don’t care ver much about 3.0.0 since I was never able to get it to run at all, and I expect a lot of problems with extensions. So keeping 2.7.x working, also with PHP 8, should be the first priority in my opinion.
Wannes Debusschere
@wdebusschere
@animaux let's see what Nicolas advises.. waiting for that
Stuart Palmer
@stuartgpalmer
We have (very reluctantly) stopped using SCMS for new projects as we do not feel confident recommending it to clients with the current state of support. However, Symphony remains GREAT and the work we are doing in Laravel to fill its place takes much longer (and is less fun). A stable and supported version 2.7 with no new features would be amazing and I'd love to continue using it.
Juraj Kapsz
@jurajkapsz

I've tested @petertron 's SCMS 3 version about a month ago, there were no problems with installing it and running under PHP 8. But that was only pure SCMS 3, with no additional extensions and I haven't tried out everything in the backend. All of this I plan to do, also want to make additional fixes when I'll found any, e.g. symphonycms/symphonycms#2926 bugs me a lot, but that's the least concern to fix. I am optimistic about having a running updated SCMS version. I also find quite intriguing @pointybeard 's extended SCMS version, will check that one as well. Anyway, I want to start with some extensions update, like the mentioned multiupload field, I only have to play a bit with git repo there; webp support I should have already nailed, want to deploy it on a live site, will send you link then.

About the idea of expanding or supporting community, I think I really miss some full fledged tutorials e.g. on how to build a site, how to constitute xsl templates the best way / best practices for xsl, example code etc. Maybe I was not on official site in years for that matter and forgot (I mostly browse API docs there and no other content for some time now), I am sure you can find lots of bits of informations on xsl in forum post but maybe nothing sumarized in one - even if a long - article. Maybe I know a trick or two about XSLT, but I am always happy to improve. Or on how to create your own extension etc. I think, if such a content does not exist yet, it would have its value and it could live easily outside offic. symphony site, which is not being updated for the time being. I find good documentation is the cornerstone for a growing potential of every project. I believe it takes a lot of effort to create such or any documentation at all.