-
Posts
10,902 -
Joined
-
Last visited
-
Days Won
349
Everything posted by adrian
-
Hi everyone, I just added multi-language support to this module. I use it with alternate language file fields for translated versions of PDFs. In my example, I have these two fields: document_pdf document_pdf_portugues I am using this filename format setting: {$page->title} Now when I upload, the PDF gets renamed to match the title of the page based on the language suffix of the field, eg. a page with these multi-language titles: My Document Title (default) | Meu Título do Documento (portugues) results in pdfs named: my-document-title.pdf | meu-título-do-documento.pdf Please note that I am still pretty new to this multi-language stuff, so let me know if you have any problems or have ideas for improvements.
-
@antpre - Tracy has an easy and safe way to disable all autoload modules for testing if there is some interference: https://processwire.com/blog/posts/introducing-tracy-debugger/#module-disabler-panel That might help to narrow it down for you. Also, with Tracy on, you don't really need debug mode
-
Problem with multi-instance giving array notice
adrian replied to asbjorn's topic in API & Templates
Yeah, that would make sense since it's an array. Will have to wait for someone who has some experience with multi-instance to chime in. -
Problem with multi-instance giving array notice
adrian replied to asbjorn's topic in API & Templates
You guys are mentioning an array rather than an object is being returned, so I am probably not correct here, but might be worth a shot - I wonder if outputformatting is off when calling a field from another instance? Try turning it on for the page, or using: $page->getFormatted('title'); Again, I a, probably wrong, but I haven't played with multi-instance yet so just throwing an idea out there. -
Given the underwhelming response I am going to assume that not many people are using this module, so I am just going to update the Github repo with the new version. I used it a LOT yesterday and it seems to be working great with the new Table pagination feature. I have removed 2.7 and below from the compatibility list for this module. It is now only 3.x (or 2.8). If you need the old version that support 2.7 and below, you can grab it from this commit: https://github.com/adrianbj/TableCsvImportExport/tree/b83df4d13fd18fcb6c4bc8ac467e6ae35cba9711 Hope some of you out there will find the new version useful.
-
Sorry, I misunderstood - I actually don't remember the difference between the two in this regard, but glad you have what you need now!
-
Adding custom Listers is one of the Pro version's key features. In the normal version it is for Pages > Find and the Users page and not for your own custom configuration. Hope you enjoy the pro version!
-
Yeah @ryan needs to start pointing this module to the new repo: https://github.com/processwire/processwire
-
-
So you want the fields from the content tab to still be there, just not the tab "button" (for want of a better description)? That sounds more like a job for CustomAdminFiles or maybe a feature request for AOS? This module hides entire tabs, including their content. Am I on the right track now?
-
Hi Ivan - not sure I am understanding - do you want to hide all tabs, or do you have some custom fieldsettabs that would still be displayed? I could perhaps implement, but if it's a case of just not wanting a tab named "Content", don't forget that you can actually rename this. Does that help, or am I not understanding your scenario?
-
I would absolutely love this - thought about it a few times, but never got started on it. This might be too much / too hard, but I'd actually love if it was more than just date/time, but actually allowed us to use all MySQL operators in our selectors. But I haven't really thought through what would be involved in making this possible.
-
Hey @teppo - not ignoring your pings, just busy and not really sure why that notice is appearing either. I saw it a couple of times today, but was too rushed to investigate, and now it's not showing, but I will keep an eye out and when I see it when I have a spare moment I'll try to debug.
-
@mel47 - I am definitely curious about the interaction you seem to be getting with Tracy and url segments, Based on your edit it sounds like you finally understand how url segments work, which is great, but we do need to figure out all those /bookmarks/ you are getting. I have seen a single /bookmark/ before but it wasn't related to Tracy. Any chance I could take a look at the server that is doing this, with instructions on what page to be on and how/where you are making that bd() call? It's late here, so I won't be getting back to you till morning.
- 6 replies
-
- url
- urlsegment
-
(and 1 more)
Tagged with:
-
I like to think we are ahead of their pace Those guys don't have a console panel, or a persistent dumps recorder, live template tester, or any of the other cool goodies that we have I'll see what I can do - I agree it would be nicer to not have to write the array with the keys for those options.
-
Hi everyone! The latest version makes use of the Tracy core's LIVE dump feature in several places, including the PW Info panel, the Template Resources panel, and whenever you use bd() From my initial testing this seems to have made huge differences in the size of the DOM required by Tracy, especially if you have a heavy page where before the PW Info panel (especially if you had the objects displayed) could be huge. It is also magic when you want to do a dump with a custom (greater than default of 3) depth, eg: bd($page, 'Page Object', array('maxDepth' => 10)); What was 29MB is now only 3KB - that's right, I have got those MBs and KBs correct! Once you start expanding the object and drilling down into, the rest of the object is added to the DOM as needed - very clever indeed! Anyway, please let me know if you find any problems with this change.
-
As mentioned in that first post:
-
Sorry, I must not be understanding - take a look at the screenshots in the first post - they show the options for defining the content for each field. I guess this is not what you are talking about though?
-
Using the get ID can be problematic / dangerous - at least make it safe by sanitizing it with: $page_id = (int) $this->input->get('id'); You might want to take a look at how it's done in the field itself: https://github.com/processwire/processwire/blob/master/wire/modules/Inputfield/InputfieldPageTable/InputfieldPageTable.module#L137-L138 Note the sanitized get id check with a fallback to getPage() of wire->process
-
No problem - understood! Do we agree then that it's not an issue with this module, but rather with the setup in your wireMail sending module?
-
I haven't checked, the code, but I would assume: http://dev.mysql.com/doc/refman/5.7/en/optimize-table.html
-
I am going to need more to go on here. I have been using this module on all my sites (on several different PW versions) since I created it. I don't suppose you could give me access to the server to take a look?
-
Are you using this with the frontend user module? Are you adding the user via the API or admin? Is the test send working ok?
-
Maybe you are expecting it to populate the page's fields in the admin? This module is not designed to do that - it generates content when viewing the page on the frontend - this way your database remains unchanged and once you populate the field on the backend, the module leaves that field alone. Or if I am mistaken, perhaps it's a PW 3.x/2.8 issue? I haven't had a chance to test with these yet.
-
Hi everyone, I have spent quite a bit of time today getting this module working with the new pagination functionality in the Table field. I have tested it in a variety of import (append and overwrite) and export scenarios with standard as well as page fields (radios, checkbox, selects, etc) and it seems to be working well. The trouble is that this new version will only with with the new version of the Table field. It will work even if pagination is not enabled, but it won't work with older Table field versions. I would really appreciate it if you guys could test and let me know how it works for you. I'd like to get this pushed to Github fairly soon, but it's such a major change that I would like some additional testing first. Thanks! PS - this update also add support for line breaks in textarea fields - I added the same CSV parser that I recently added to my BCE module.