Jump to content

flydev πŸ‘ŠπŸ»

Members
  • Content Count

    1,033
  • Joined

  • Last visited

  • Days Won

    31

Everything posted by flydev πŸ‘ŠπŸ»

  1. Recently @Wanze starred a free app on Github, just awesome : https://github.com/responsively-org/responsively-app It's a browser modified that show how a website work in all selected devices. I think a lot of people will fall in love for this soft - give them a star on github πŸ˜‰
  2. Welcome here Seema, you just spot a damn good community, ready to help and share in a professional fashion πŸ‘ Where are you from (if its ok) ?
  3. Just a heads-up on this, Really strange, when using nested hannacode, each nested hannacode add 100ms to TTFB. I saw old issue on Github and a commit about nested hannacode but I ask myself if it was tested with a lot of content and something than more than 30 hannacode in the same body field. I used RockReplacer from @bernhard and the whole page load in 200ms instead of 1.8s. It was used like: [[tag element="div" class="row"]] [[tag element="div" class="col-6"]] $content [[end-tag]] [[end-tag]]
  4. @Bike welcome on the forum. Use this search/tool : https://cse.google.com/cse?cx=014789015761400632609:fxrf0rj4wr4 Then check theses threads : Then come back here after some read πŸ‘Š
  5. I found what I was trying to remember. Try what is said in this thread, last answer, it seems it's a related issue (I have the same one in a setup). Direct answer: Modules order in the db.
  6. after a backup, I would delete session files in site/assets/sessions and clean entries in the db, table `session_login_throttle` before going further.
  7. @adrian I spotted something quite "annoying". Check the line number on the bottom of panel. It doesn't show anymore. Before : After : The line is shown only when I over the link with the mouse.
  8. I thought I was in Tracy's thread sorry πŸ€¦β€β™‚οΈπŸ€£
  9. Oke thanks @Klenkes Then he should also verify namespaces on the templates / modules following the stack-trace. I have an issue like this on an install, due to a namespace error, I have to rename each modules called then installing it again.
  10. I don't know why you have this module in `site/modules`. 1 - make a backup 2 - rename the folder `FieldtypeTextareas` to : `.FieldtypeTextareas` and refresh modules, then if you are invited to select a module between `site/modules` and `wire/modules`, choose the last one. 3 - report here
  11. I just hit [enter] at the end of the line, like in CKEditor, a new paragraph is open.
  12. I will edit the post, but it's just to show you that is possible to move easily blocks. For the pros/cons you exposed, I have the same point of view and I still think that CKEditor should stay the default editor in ProcessWire. Look at this screencast : Enregistrement #3.mp4 CTRL/CMD + C, S, X ok πŸ‘ Interesting, what you mean exactly ? That's clear this is something to deal on client basis. Example on personnal experience : - Me, as I am not a content editor, I still prefer to use CKEditor. - A colleague, writing big wall of text, is scratching his head on CKEditor and edit content on Wordpress then paste it in PW πŸ€¦β€β™‚οΈ
  13. Look like you have to call $res = paymentCheckout() which return an array with the form. Then you just echo the form (echo $res[0];). https://github.com/benbyford/PaymentStripeIntents/blob/master/PaymentStripeIntents.module#L62-L139
  14. Just a small question about payment gateways. Have you a plan to release something like an abstract class to be able to be ready on the lunch of the version 2 ? I made last week a module to manage payment trough VivaWallet which I would like to port to PadLoper v2 asap.
  15. As its stated, you have to do a "repair". Make another backup, then start the repair procedure (quite simple on MyISAM tables). To find the cause, you should check logs about hard-drive failure or a server crash, or ask the support if they encountered issue on their side.
  16. I must admit that this is something I had not envisaged.. my mind was focus on people existing contents πŸ‘
  17. You are all right and everyone have good arguments. A page builder should be built IMO. As a recent example, I needed to build a cool invoice, like the one you receive in your inbox sent by big companies names. Their email look so fun/cool/responsive that YOU WANT TO DO THE DAMN CLICK on their call-to-action button. Then I found a cool software called "Nicepage", where you move blocks, edit styles and content, and tada, a cool page done in a minutes, with clean code, really - after a copy-pasta moment, I had my invoice in my template sent by PadLoper. I think it's @Jonathan Lahijani that was saying something in this, users which build marketing pages, landing pages and other things like that, it's just incredibly useful. Another example, I don't build website everyday anymore, but backends (based on ProcessWire) with public/restricted API and desktop/mobile apps connected. I can imagine how easy it could be to extract/manipulate data from an external apps (What's happened with EditorJS). Plus, and even if it's not the primary goal, given the tool we already have in our hand, it will make a bump on new users/devs which will use ProcessWire. The right ones ? not sure, maybe the forum will be spammed by "unexperienced user" which will try to build a website with the builder but doesn't understand in first instance how to apprehend ProcessWire. But it should be developped keeping in mind what all the devs say in their different horizon. I mean, a system of permission should be built-in, every blocks or type of blocks should have a permission, restricting some functionalities that could be used in an editor, or the page builder it-self. Eg. all blocks are available to superuser, but other users will have only access to the defined blocks for their role combined to the restrictions of the page being edited. "I don't want to give so much freedom to my client because he will ruin the front-end" Absolutely, but is your job to lock everything. Building pre-defined blocks (speaking styles, not content (even if you should limit content)). - Give them possibility to write their article, and to add a block with three columns for 3 featured products of their webshop. So cool. - Give them possibility to write their article, and to add a banner/call-to-action newsletter. Here you limit the number of words/paragraph, whatever, then again, So cool. And IMO, it doesn't change anything at this time of writing: with or without a page builder, clients are often asking more and more. Where I see a benefit to give the user the ability to add / remove blocks from a page builder is the ease and feel when editing content - productivity in addition. It depend also on how large is the project, the client's technical background, if there is a team or not, a frontend dev on the team or not. Given this factor, you have to "educate" your client in consequence. This imple to explain to the client, how/why it can and howtonot/whynot it can. To each one his field of work and I think this particular argument should not stop any idea because it is valable for whatever special you make for a client purpose. You will have on the next weeks a preview of EditorJS which maybe will give you more idea/insight on how to work/render/restrict theses data blocks.
  18. Hi guys, Yes I know that half a year passed; I have a colleague too which put pression on me to finish it. To be honest I got at least two months without possibilities to get my hand on it and thus to finish it as I am overwhelmed by a project for the works which take all my time. The project is far from being abandoned ! As I said early I would want to give you a professional module, and in the same time, I would like to avoid to be submerged by issue due to a release which should have been released later, I mean in a stable and tested one. What is missing : - multi language support (I personally need it asap) - front-end editing (I decided to put this feature in standing mode and will be released in a future version) What is missing which make the module "un-releasable" right now ? - I need to handle existing content - and this last one need to be brainstormed hard. There is so much case to be taken into account - as every setup can be different. I think that a module to import/convert existing content, which could work like Ryan's import/export page feature need to be shipped with EditorJS.
  19. Hey @Jonathan Lahijani this snippet is super useful, but I encounter an issue. I have a body field with 3895 words and some call to this hannacode to build Bootstrap columns. The issue is the following: Wihtout the snippet, the page load in 200ms. With the snippet, it load between 1.8 and 3 seconds. Any idea ?
  20. Hi @Robin S Since the last update (0.2.0) I get this exception when I set a custom hook : Fatal Error: Uncaught TypeError: Argument 1 passed to BreadcrumbDropdowns::pageEditBreadcrumbs() must be an instance of AdminThemeUikit, instance of AdminThemeCanvas given, called in site/modules/BreadcrumbDropdowns/BreadcrumbDropdowns.module on line 117 and defined in site/modules/BreadcrumbDropdowns/BreadcrumbDropdowns.module:221 #0 site/modules/BreadcrumbDropdowns/BreadcrumbDropdowns.module (117): BreadcrumbDropdowns->pageEditBreadcrumbs(Object(AdminThemeCanvas)) #1 wire/core/Wire.php (397): BreadcrumbDropdowns->modifyBreadcrumbs(Object(HookEvent)) #2 wire/core/WireHooks.php (927): Wire->_callMethod('modifyBreadcrum...', Array) #3 wire/core/Wire.php (465): WireHooks->runHooks(Object(AdminThem (line 221 of site/modules/BreadcrumbDropdowns/BreadcrumbDropdowns.module) This error message was shown because: you are logged in as a Superuser. Error has been logged. Sorry I didn't got the time to investigate. I am using the custom theme AdminThemeCanvas.
  21. remove this comment : https://github.com/processwire/processwire/blob/master/htaccess.txt#L173
  22. Ok I understand better your issue, I don't have time to test it, but something to try is : AddHookAfter Modules::refresh to call upgrade($fromVersion, $toVersion) "This method should make any adjustments needed to support the module from one version to another." If you give a try, please report back as I am curious now πŸ˜„
  23. Hi @modifiedcontent It's really easy, and I suggest you to copy the MyCommentForm.php file from /wire/fieltype/fieldtypeComments, put it in your template directory then rename it to _MyCommentForm.php and modify this file to your need - for you it's the renderFormThread() function which is interesting and there to be tweaked. Then in a template, you put the following code : include("./_MyCommentForm.php"); CommentStars::setDefault('star', '<i class="fa fa-star"></i>'); //<= star item using fontawesome icon $options = array(...); // options of your form, check `myCommentForm.php` $myCommentsForm = new MyCommentForm($page, $page->comments, $options); echo $myCommentsForm->render(); You have also a good function to start here to control all the comments markup : An screenshot of what can be done (sorry for the screencast, I can't resize it.) Enregistrement #3.mp4
Γ—
Γ—
  • Create New...