• Content count

  • Joined

  • Last visited

Community Reputation

29 Excellent

About PWaddict

  • Rank
    Sr. Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

930 profile views
  1. Wow you fixed that issue. Now it's working properly. Thank you so much
  2. It seems that the module isn't working anymore on websites without languages core modules installed. I've upgrade the module from 2.0.3 to 2.0.7 on a live website (without languages core modules installed) and when I tried to add a page that used by this module the page didn't even saved as unpublished and there was an error. I forgot to copy the error cause I was in hurry to switch back the module to the 2.0.3 version. I hope @kixe can fix it.
  3. Use the Global Options for Embedded YouTube/Vimeo Videos module to add player parameters.
  4. If you want to set maintenance mode only in database follow this guide otherwise for the entire site install the Page Protector module.
  5. Any news about the fix? Thanks. Note: The problem happens only on multi-language title field. If use a regular text field everything is working properly.
  6. Yes, I have the 2.0.7 version. I found the issue. I'm using 2 fields on "Name format for children": title tour_date All these time I was only posting a title on default language. The only way to get the correct date format is If I post a title on an additional language. Can this be fixed from your module?
  7. For me it's still not working All the page names having the format value from the default language. Thank you so much for updating the module with this feature. I hope I will figure out why it isn't working for me. I'm on localhost with php7 and the pages are created from a pagetable. Do you think any of these is causing the issue? My site url on localhost is http://localhost/mysite/ and I'm thinking that the problem might be that. For example the module "Admin Custom Files" can't inject the files properly on that url. Somehow can't see this part: /mysite/. On a live server it's working properly. So, maybe your module too can't see the correct urls of my additional languages. I have to upload it on a live server to make sure if that's the problem. Thanks again. I will let you know if I find the problem.
  8. @kixe Can you please confirm that the below example is working for you? If you have %b %d %Y on the default language and %d %b %Y on the additional language are you getting these formats on their page names? default: oct-17-2018 german: 17-okt-2018
  9. @kixe I'm suggesting you first to try to get ONLY the regular date format values from additional languages. Add on the default language: M d Y and then on additional language add d M Y. When you managed to get that values correctly on page names then continue by adding the code for setlocale and the strftime format values: %b %d %Y on the default language and %d %b %Y on the additional language.
  10. @adrian When you get back online please fix the below issue: Problem: Removing the title from an additional language the page name doesn't switch back to default's language name. Solution: You have to remove this update. You added that cause @videokid had problem with the Greek characters. If someone wants to replace non-latin characters there is a module on PW Core modules called "Page Name". There you can add for example the Greek characters to convert to latin characters. Like this: α=a
  11. @kixe My locale settings are correct cause datetime formats on front-end are working fine. Even on the module datetime formats are working fine if it's on the default language. I wish I knew how to modify the module to get the correct datetime formats for the additional language too. Here is exactly how my translated "C" string value is on each language: Default en_US.utf8, English_United States Español es_ES.utf8, Spanish_Spain Deutsch de_DE.utf8, German_Germany Note: The first value is for my server (Linux) and the second is for XAMPP (Windows). You should replace your en_EN to en_GB to get the proper value. As far as I know the en_EN isn't a correct locale. When you said that you've tested the translations you meant on template just like on your example above or in the module?
  12. On my test site my default language is english and having 2 additional languages (spanish & german). All the language page names are getting the english format. If I switch the default language to german then all language page names are getting the german format and so on...
  13. I've tested the new update and It doesn't work. All the language page names are still getting the default language datetime format.
  14. Thank you for the update. It works great. I'm settng the locale by translating the "C" string on LanguageSupport.module on each language which is the easiest method. The other method would be to add a field for locale inside the system's template "language". I've changed the default's language locale from english to german and the module updates the page name from oct-17-2018 to okt-17-2018. So PW is aware of the datetime's language. Do you think you can get the locale from the "C" string on LanguageSupport.module or from a field under the template "language" so the module can update the additional language page names too?
  15. @kixe There is one last thing that I think needs to be fixed either you're using multi-language datetime formats or not. The page name for all languages has only the default language's datetime format. If you can make it grab for the additional languages their datetime formats that would be perfect.