Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/01/2018 in all areas

  1. Update: Seems like I'll switch to agGrid for my module. It is also MIT licensed in the basic version. It can handle multiple thousands of rows (loading 30k rows with pages->findObjects needs 6 seconds here; 10k pages = 800ms; without caching, of course) It has very nice filters built in (contains, starts with, not equal, etc) It is easy to create custom filters -> the regex filter is built by myself It has the possibility of custom cell renderers (see the percent bars; though I will have to adopt how this works for my module) It looks cleaner then datatables It has CSV export that seems to work just as good as the excel export of datatables (it is also possible to modify the cell values before export) I managed to rebuild the column statistics functionality (for all rows and only selected rows) that I have built for datatables. This is a must have feature, making it easy to show eg. the sum of all revenues in a specific month. It is pure JavaScript, so no dependencies have to be installed. It should also be possible to use this module on the frontend quite easily. Only thing that I'm missing from datatables is an easy way to access data. datatables seems to be superior in this regard. But I've also rebuilt this functionality making things like this possible, showing the average value of the grid's "rand" column, taking into account all filters and returning all rows (not only selected ones): return grid.avg('rand', {filter:true, selected:false}); This statement is used for the stats row at the bottom of the grid. Todos: Action items for pw-panel editing Anything else that you think is necessary?
    5 points
  2. Use only one translation per line.
    2 points
  3. Ok guys, I get what you mean, so what about a module with this flow ? monitor and log HTTP error code for a period if an entry / request is superior of N then backup .htaccess file (versioning it) add new entries to the .htaccess file Does it make sense or I should let the user manage their .htaccess file manually with a FAQ or something ?
    2 points
  4. Try: <?php if ($page->id == 1 ) : ?> <div>your content</div> <?php else: ?> xxx <?php endif; ?>
    2 points
  5. I will share the code when it is ready (not sure if ever... ) Currently I am exploring the possibilities. Chances are really good thanks to the great ProcessWire "ecosystem". Thanks for the mention in your document. I will read it through tonight. >Will this also handle the case where you have full bleed rows with contained columns on the inside? Not sure what you mean? Nested columns? The next step is already underway: Inline editing in the backend. (It is not yet saving, I hope tomorrow...). http://theowp.bplaced.net/upload/prev2.html Thank you.
    2 points
  6. In all honesty, I think that Jumplinks is better suited to site migrations. Black holes should either be covered by a specifically-built module, or by htaccess/vhost config...
    2 points
  7. Today's update: The inline editor for the backend can now save the changes. And the visual resize tool works now on the breakpoint which corresponds to the current screen size. So you can define the layout for every size visually. http://theowp.bplaced.net/upload/prev3.html
    1 point
  8. /old-dir/{all} -> /new/ was exactly what i was looking for. thanks!
    1 point
  9. @ngrmm - if you're wanting to redirect /old-dir/* to /new/*, then you can use the following: Source: old-dir/{all} Destination: new/{all} {all} is a smart wildcard (https://rockett.pw/jumplinks/smart-wildcards) that equates to {all:all}, which matches anything and everything, until another wildcard or marker. So, /old-dir/child-a/ will be redirected to /new/child-a/. If you need the path after /new/ to be omitted, then just use new/ as the destination, and then /old-dir/child-a/ will redirect to /new/.
    1 point
  10. Hi psy and pideluxe, thanks for your responses. I took the first solution. Processwire is cool for learning php. thanks P.S. For all php newbies: http://php.net/manual/en/language.operators.php
    1 point
  11. Depending on your use case, here's two other options Clone PageAutocomplete, rename the file and class, .e.g PageAutocompleteCustom, edit it to do what you need. The advantage here is portability, no need to Hook into anything, get to know the inner workings of ProcessWire (especially Pagefields, etc). Lister/Lister pro: This option depends on what you mean by 'keyword'. If it means some other ProcessWire property, you can easily filter results in Lister using various criteria
    1 point
  12. My personal preference is not to update the .htaccess file automatic. If something breaks, the complete site may become unrenderable. Also warning mechanism may not get invoked then(!). Additionally I only allow read access to the file for security reasons. So my favourite would be to collect candidates and provide them as alphabetically sorted markup on demand
    1 point
  13. Thanks for sharing your video @Jonathan Lahijani! In case your interested, I added your technique to my "Techniques for flexible page layouts in Processwire" document https://docs.google.com/document/d/1peY-FUpevKgy87cKOxIVz8jwcv2-3c61zbiJr3QKO6c/edit?usp=sharing
    1 point
  14. Great work @theo! I'm interested to see how this plays out. Will you be sharing the steps/code used to make this? I added your technique to my document "Techniques for flexible page layouts in Processwire" https://docs.google.com/document/d/1peY-FUpevKgy87cKOxIVz8jwcv2-3c61zbiJr3QKO6c/edit?usp=sharing. Will this also handle the case where you have full bleed rows with contained columns on the inside?
    1 point
  15. I use Redirect gone ... in .htaccess Redirect gone /wp-login.php for all that stuff. (First I log 404s for a period, than I add those candidates to the .htaccess, before ProcessWires entries!!) I think it is better to not invoke PW for this stuff, (lesser overhead on the server!), instead use apache custom error page(s). 47ms is fast! PS: 410 is better than 404, as I also use this for SearchEngineRequests that try to reach URLs that do not exist since 10 years or so. Normally the SEs should flush their cache on 410 returns.
    1 point
  16. Hm, I have "pages loaded: 23" $config->debug = true/false does not make any difference. Only difference is when I hit the "Disable Tracy" Button in the Debug Bar it instantly becomes fast as usual. I can send you a site profile, maybe that helps
    1 point
  17. Awesome!!! Thanks!! Thought I've read the whole docs and examples and googled for an hour but found nothing... now it will be a lot more fun working on this tomorrow Maybe I should change the topic title to "everybody who can rtfm better than me, raise your hands" ??
    1 point
  18. A short update this week looking at ProcessWire 3.0.97 and a preview of coming attractions: https://processwire.com/blog/posts/processwire-3.0.97-core-updates/
    1 point
  19. @bernhard Have you seen this https://www.ag-grid.com/javascript-grid-reference-overview/#listening-to-events?
    1 point
  20. I don't see any suspicious information in the panel. Only the HTML code of the debug bar is totally bloated. I think the simplest is to test it on your own. I'm running a fresh dev installation with blank profile and tracy v4.9.33 I've just created a page "data" under /home and added 30k pages with the tracy console: for($i=0; $i<30000; $i++) { $p = new Page(); $p->template = 'basic-page'; $p->parent = $pages->get('/data'); $p->title = uniqid(); $p->save(); } Then when I open one of those pages in edit mode the tracy bar takes 10s to load..
    1 point
  21. good guess Debug Mode is also very slow, but only if Request Info is ON. If Request Info is OFF the Debug Mode is 10ms (first screenshot)
    1 point
  22. Hello Neo, are you in the Matrix already?
    1 point
  23. hey @adrian I'm working on my DataTables module (that might get renamed to RockGrid btw because I'm experimenting with another grid software ) and have 30k sample data pages (basic-page with only title field). When I open such a page in the admin, the page load takes very long (around 10s). I looked at the network tab and saw that the request for initial page load (?id=1017) loads 5.7MB of data. Cookie: pagelist_open=JSON%5B%221-0%22%2C%221016-0%22%2C%221017-0%22%2C%227-0%22%5D; wire=...; wire_challenge=...; tracyCodeError=ERROR%3A+Maximum+execution+time+of+120+seconds+exceeded+on+line%3A+454+in+D%3A%5Claragon%5Cwww%5Caggrid1%5Cwire%5Ccore%5CWireDatabasePDO.php When i switch off tracy the page load is instant. The code for the debug bar is huge: Any ideas which feature of the panel is causing this behaviour? Thanks in advance, no hurry at all with this one
    1 point
  24. Under Edit field > Input > CKEditor Settings > CKEditor toolbar, you need to add the button: A11ychecker Save, then you should see the new button
    1 point
×
×
  • Create New...