ceberlin

@ nico ( "How to add custom translations for e.g. modules?") That is a really good question and maybe another reason for a module. What about the possibility to put individual files to the LANGUAGES (copied by the click of the mouse over from the module) which overwrite the standards so that you can maintain individual translations if needed. Advantages: your individual strings would survive language updates from the module - that eliminates the risk of updating languages the number of files that need individual treatment are probably not so many (opposed to the 500+ files right now) (This all is a loud thinking - not a finished concept yet)

(This discussion is moved here from the GitHub issues board) The discussion ended by considering of moving the admin language files to a module (maybe even aware if the translations are for the regular version or the DEV version of ProcessWire). You comments and ideas are highly appreciated! --- DISCUSSION SUMMARY FROM GITHUB: tbba (ceberlin) wrote Today I had the honour to remove admin language translation files from the default language to have that back to English. That ment clicking the trashcan a 500 times while paying attention not to remove anything else but those admin language files. (Well I ended up doing this in the database directly as a workaround.) For the Wishlist: Why not adding a button where all instance that start with "wire--" have the trashcan seleced automatically. Or better: I would prefer at least to have them in a separate repeater list so that I find my own frontend translations and those settings by site--modules like supersmartypans easier. Or even better: why not separating Admin translation files to a module somehow so that installing/de-installiing, updating(via ModulesManager!) and switching them on and off is much easier? ryancramerdesign commented Double click the trash can and it'll mark them all for deletion. tbba (ceberlin) commented Thats cool. I did not know that. There is still the possibility of deleting too much (site-- stuff). What about the idea to separate the site-- files from the wire-- files? Wouldn't that be much easier? EDIT: And a module for the wire files would make the updates over the modules manager so easy. No more dropping of tons of files - and alerts when they are outdated. NicoKnoll commented I think it probably really makes more sense to change language packages to modules which are requiring "Language Support" to be installed. Pros: easy updatable makes my module "LanguageInstantInstall" obsolet because you just could list al of the languages which are in the module directory with "module manager" It's more the ProcessWire way of being modular Cons: How to add custom translations for e.g. modules?Maybe that's something for 2.6. tbba (ceberlin) commented A module would have another advantage: There could be something implemented that matches the translations to the PW version. Right now, using the DEV version could mean: not matching translations. But - thinking loud - there could be a DEV version of the language files on GIT that then matches with the PW DEV version - and the module selects the right one. ryancramerdesign commented I agree, language packs as modules would be nice for the future. Like Carl mentioned in splitting site and wire files, perhaps language pack modules would be for wire, and the existing storage system could be exclusively for site.

I wonder if PW becomes vulnerable to the XML Quadratic Blowup Attack (as Drupal and Wordpress were), in connection with XML-RPC... src: http://mashable.com/2014/08/06/wordpress-xml-blowup-dos/

There is another issue, but only on one installation. Here the module does not install properly this time.... Notice: Undefined variable: parent in /Users/carl/WWW_TESTSERVER/ullewaeh-git/site/modules/ProcessPageDelete/ProcessPageDelete.module on line 187 As I said the older versions of the module worked flawlessly.

ok, de-installation worked with commenting out the uninstall function. I got a message that hooks were removed. There was no "delete page" subpage in admin/setup/pages/. There was one in admin/pages/ - hope that's the one to delete Then I re-installed - de-installed and re-installed again. Works! - Can I invite you to a beer?

Hi Nico, that would explain that newly installed versions work, old installs not. I use ModuleManager do keep Modules up-to-date, your module is the current version. Since this is a standard module I use often when setting up things, this is a very old install, with various updates. So if you changed something with the install routine in the meantime, this might not be compatible with old installs. I wonder how to de-install this best - the brute-force way. Trashing the files and removing the entry from the DB table "modules" is probably not enough...

Hey Nico, this thing is mysterious. With the same setup (PW dev 2.4.9) it makes a difference whether the module was already installed or not: a) If not already installed, I can install it - and later on de-install it again: no problem. b) If it was installed - and it normally is here because It is part of my PW startup profile for new projects - then this conflict appears. My normal workflow is to de-install this module as soon as I am finished with building the site and editors start using it. That's why I know that this issue wasn't always there. Do you need more info from me?

On one installation (using PW dev 2.4.9) I cannot uninstall this module any more. TemplateFile: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'delete-3' for key 'name_parent_id'

Sometimes the thumbs appear cropped on hovering the thumbs links during page-edit. Maybe some css z-index or overflow:hidden thing. - I am using the PW dev version. Do you need a screenshot example? Is there something you can do about it? (Sorry this was mentioned already earlier in this thread. My post can be deleted, if you wish.)

Very cool and right in time! - I was just about to hacking the original code to make it work in German. Your solution, using language translation files, is VERY SMART. - Works well so far (tested with PW dev, German/English). Thank you very much for this contribution!

+ 1 for leaving it like it is and not changing values automatically here. ... but maybe add a hint that there is a publishing-field active that would result in a re-publishing (if that hint isn't there already, is it?)

Hi, sure I know that deleting the rows in the database solves it perfectly. My post is -because I think to remember that there was a max_age setting somewhere (but I cannot find it) -and because a Delete-All button is something I was used to from Drupal and liked the idea to have such a button.

Maybe this was answered and I only did not find it.... I am thinking of adding a folder to the admin/ like admin/tools/. I want to have everything inside of this folder accessible to an editor. I would then move certain pages from modules there, like "changelog". What would be the recommended way to make this work?

just a quick question... How do I set the max age (bzw. where can I reset the log)? (I want to handover a site to a client and want the millions of log entries during dev to be removed up to a certain date.) I would expect a "delete all" on the listing page - did I overlook something?

Picked up from GitHub for discussion... https://github.com/ryancramerdesign/ProcessWire/issues/489 Probably I did not make my point clear. Assuming that commenting on closed issues at gitHub a waste of time I want to present my idea here on the wishlist to find supporters for that idea... ------------------------------------- Example task: The default general field description is: "fill this in" In the current template the local field description is overwritten with: "fill this out". Now I want to reset the local field description with the general description. (The "description" is just an example. The same applies to all other entries and settings that can be overwritten) What I tried out: Deleting the local description means: nothing is shown. - This is a good and intended behavior, as overriding something with and empty field can make sense in many cases. Writing what I want to have there, works. How to archive this now (I quote Ryan): This works fine but can be a tedious task to do manually. Wish: Especially when building large websites or in teams or half year later the question can come quickly: what was the original value again? A "discard local changes" would make that comparison easy. Then I could either save or not save that reversion, depending what content version I prefer.

nicode.eu nicode.me nicode.co

Yes it's funny, but for non-English natives a less cartoonish narration style would distract less from the great news content and it would be easier to follow, i.m.h.o.

Hi netcarver, sorry for not replying earlier. I somehow overlooked it. I tried your code update - and from my quick testing it seems to work fine now. Thank you very much!!!!

Just a quick note: On LOGIN ERROR (im my case a Session Throttle interception) the module sends a list of notices for the login screen: Notice: Undefined index: debug in /.../site/modules/TextformatterTagParser/TextformatterTagParser.module on line 207

Sometimes it helps to delete everything within the Cache folder. Did you try that already?

Is there a limit of how many AsmSelect I can use on one page? I am asking because I have a settings page with 6 ASMselect (with only a few selections each) and one is starting to misbehave: It can only remember the first 2 selected pages and forgets the rest after each page save. Looking at the database I see 3 ids stored for that field, which is correct. But only 2 are shown in the admin and read via the api. (My only other explanation for this mystery bug would be damaged pw indexes of the database.) Update: The problem only occurs if AUTOJOIN is set for the page field.

Yes, exactly. Am I the only one with that module and update trouble? Then I will dig further.

Hi Soma, there is one mystery left with a module which insists to be outdated although it's not. No idea what that is. The effect is on all my processwire installations. I left a note in the modules section of the board already... Found following updates for installed modules: Module: FieldtypeCropImage v1.0.2 Found new version available: v1.0.3 More infos at: http://modules.processwire.com/modules/fieldtype-crop-image/

fmgujju, The info at the top of the modules page should say something like: Modules found on modules.processwire.com (224) Maybe the file limit in the module's prefs is to low to check for all availabe modules? I had to increase the limit at my installations recently.

HI Allesio, I am right now evaluating the module for a project. This project has languages. My questions: RIght now the stopwords list is hardcoded into the modules folder. In case I add or change anything there, it would be lost after an update of the module. Correct? Isn't assets a better place for the stopwords? - Or the database? What do I do if I am in a multilingual environment. How can I set stopwords per language? Can I at all?