Jump to content

ceberlin

Members
  • Content Count

    472
  • Joined

  • Last visited

  • Days Won

    1

ceberlin last won the day on June 15 2015

ceberlin had the most liked content!

Community Reputation

252 Excellent

About ceberlin

  • Rank
    Distinguished Member

Profile Information

  • Gender
    Male
  • Location
    Berlin (Germany)

Recent Profile Visitors

7,324 profile views
  1. Maybe it could be great to add freestyle variable fields-list to add to the backend interface, in case you do not want to offer any new option hardcoded in the module?
  2. Now there is a new VIMEO privacy "do-not-track"-option, which should be always on in in the EU: ...?dnt=1 With this, VIMEO does not set a Cookie any more. Source (German): https://www.datenschutz-guru.de/wie-kann-ich-ein-vimeo-video-datenschutzfreundlicher-einbetten/
  3. I do, too. But I thought having the links placed UNDER the Confirm buttons makes more sense? And using a PW selector for the pages takes besser care that the links do not break on changes. (Text links are easily overlooked ?)
  4. For those having access to the premium area of erecht24, here is an intersting information update after the last EUGH decisons: https://www.e-recht24.de/mitglieder/updates/eugh-urteile-cookies-einwilligung-google-analytics/ The world gets more complicated every day and I think the cookie managers too. Small comments: Clicking "accept" was an agreement - so when opening the popup again later, the agreed checkbox could be pre-sected? Or better not? I tried revoking rights, but the Google "GA" cookie is still present. Is deactivating the script enough, musn't there also the Google Tag Manager cookie removed?A lso I can save "no" decision (no checkbox selected). I wonder what that means for the decision taken... I compared this with a WordPress cookie manager and found 2 nice ideas: There a simple counter of how many people opt out. There are 2 links in the pop up under the "Accept" buttons in the right corner: Impressum and Privacy. So in case those madatory links get covered by the popup, those page are still easily accessible.
  5. If allowing "debug" there is also a warning now, that does not go away: Declaration of ProcessWire\FieldtypeCroppableImage3::getModuleConfigInputfields(array $data) should be compatible with ProcessWire\FieldtypeFile::getModuleConfigInputfields(ProcessWire\InputfieldWrapper $inputfields) in //site/modules/CroppableImage3/FieldtypeCroppableImage3/FieldtypeCroppableImage3.module on line 4
  6. In my case, this was an true Error 500 Exception (not a simple warning with some sort of "self healing", as described by Ryan) @matjazp your hint about modifying the module helped. The websites are back and live. For anyone wondering which file is to change, it is this one: /site/modules/CroppableImage3/FieldtypeCroppableImage3/FieldtypeCroppableImage3.module Update 16 October: I saw Ryan tried to address the problem from his end today by updating the core: https://github.com/processwire/processwire-issues/issues/995
  7. After updating PW 3 to 1.4.1 today (PHP 7.3) I got fatal errors and had to rollback. Compile Error: Cannot make non static method ProcessWire\FieldtypeFile::getModuleConfigInputfields() static in class ProcessWire\FieldtypeCroppableImage3 (line 4 of //site/modules/CroppableImage3/FieldtypeCroppableImage3/FieldtypeCroppableImage3.module) Anyone else with this problem?
  8. 1. Your manual setting could serve well as a fallback in case there is a problem with the calculation? 2. No warning message, as far as I remember.
  9. Hi, I just stumbled upon your module. Great idea! Your obligatory settings string $config->dbInitCommand = "SET NAMES '{charset}', time_zone = '+02:00' "; is not considering summer time changes? Maybe this can be calculated from $config->timezone = 'Europe/Berlin' (or whatever), a setting which is there already in config? Uninstalling the Advanced Datetime field leaves Advanced Datetime Inputfield and Datetime Extensions installed. Is this intended?
  10. I have problems with Method 2 at our provider DF.eu (Apache 2.4): RewriteCond %{HTTP_ACCEPT} !image/webp [OR] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{DOCUMENT_ROOT}/$1$2$3/$4.jpg -f RewriteRule ^(.*?)(site/assets/files/)([0-9]+)/(.*)\.webp(.*)$ /$1$2$3/$4.jpg [R=307,L] Works not reliably on the LIVE server - Safari sometimes tries to show still WebP. On the MAMP/Mac Server it works. RewriteCond %{HTTP_ACCEPT} !image/webp [OR] RewriteCond %{REQUEST_FILENAME} !-f # RewriteCond %{DOCUMENT_ROOT}/$1$2$3/$4.jpg -f RewriteRule ^(.*?)(site/assets/files/)([0-9]+)/(.*)\.webp(.*)$ /$1$2$3/$4.jpg [R=307,L] On the LIVE server this works (3rd condition commented out). I wonder, why.
  11. Hi Teppo, is there a way to make the search language aware? - I mean getting the right context from mutilanguage fields per active language? Probably this would mean an indexing per language? If not, I wonder if at least all language text entries from a multi language field get indexed? - so a search in the non default language might find maybe too much, but not too little?
  12. The PW "Upgrades" module does not recognize those updates... it still shows version 0.3.1. as current (in my setup), unfortunately
  13. Hi Mike, the update 1.5.53->1.5.54 with the PW "Upgrades" plugin does not work (worked before). It re-installes the old version.
  14. same trouble with MAMP / MAC + PHP 7.3..... reverting to 7.2 solved it
  15. Works very well. Extremely useful! Thank you!
×
×
  • Create New...