Jump to content

Hackasacka

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Hackasacka

  • Rank
    Newbie

Profile Information

  • Gender
    Female

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Robin, We have now tested Processwire v3.0.123 and another Android v7.0 phone and an unknown version of Chrome with success. Also, an older Android tablet with unchecked versions of app also worked if you double-tap the "image description" input box. An alternative solution was to simply download the latest version of the Firefox v64.0.2 web browser released on the 9th of January 2019. Opera's web browser might be a useful alternative to try too? Regards, Hackasacka
  2. Hi Robin, Just tried the oldest Processwire version I could find on GitHub of 3.0.34 released on 23 Sep 2016. This also appears to have the same problem when you try to modify "image descriptions" in that the screen keyboard does not appear. I'll see if I can try a tablet later as maybe the screen size is an issue? Regards, Hackasacka
  3. Hi Robin, Thank you for experimenting with the mobile OS's. The Android version is 7.0 and the Chrome version is 71.03578.99. Chrome for Android Update Tuesday, December 18, 2018 Good news, everyone! Chrome 71 (71.0.3578.99) for Android has been released and will be available on Google Play over the course of the next few weeks. This release includes stability and performance improvements. This appears to be the latest version available for Android, but unfortunately this still did not work. What version of PW did you test this with and what version of Android? Regards, Hackasacka
  4. Hi Ryan, It has recently come to my attention that some "Processwire" users accessing the "admin" of their websites using various versions of the Android OS cannot add or modify "image descriptions" any more (it was possible in earlier versions up to 2.7.2 and possibly later)? Also, some of the other "Imageick" tools, which have proved very useful do not appear to function on the Android OS's trialed to date. I am pretty sure the iPhone OS was also working on later versions than 2.7.2 as I remember struggling to crop an image using it (probably PW 3.0.98), but unfortunately I do not have specific versions of PW to reference as we upgraded them as soon as PW was upgraded to 3.0.123. Also, I have tested with and without the "Admin UI Kit" to no avail yet. It could be related to our hosting environment and the versions of MYSQL or PHP, but think it is more likely to be something else? Personally, I find it much easier to use a larger screen with a mouse (I defy anyone to crop an image accurately on a mobile or tablet) and so haven't noticed this before now. Please let me know of any possible solutions to this problem as it is useful to at least have the option to use a mobile interface with "PW Admin" when roaming away from a suitable PC. Regards, Hackasacka
  5. Hi Kongondo, I have recently installed your latest Processwire "Blog" module with version 3.0.123 and included your example templates and fields. Although it is a minor issue, I thought it may help some other Processwire users to know that the "blog_tags" field (of type Page Reference) in the template "blog_post" does not appear to work in our particular hosted environment unless the "Page Auto Complete" and the "Settings specific to Page Auto Complete" are modified to the first recommended setting as opposed to the second recommended setting (Input field tab) i.e. "Contains phrase or partial word (using fulltext index) - Recommended (this 1st option functions ok). However, in further testing so far, I believe that it is a "Core" issue with this particular field type when used in conjunction with the "Page Auto Complete" option as I have been unable to get it working with "Contains phrase or partial word (using LIKE) - Recommended". As this is the default option, it may also be a problem when it is used for other purposes unless you know to change the default afterwards. Hope this is helpful. Regards, Hackasacka
  6. Hi Milenko, Here are Ryan's instructions on how to perform a manual upgrade :- https://processwire.com/docs/install/upgrade/ Please note that it also mentions the "index.php" which would require replacing too. Kind regards, Hackasacka
  7. Hi Theo, Just to confirm that "mod_security" was indeed the problem on our particular hosting environment with the "ProcessWireUpgrade " module downloading the requisite .zip file for upgrade to the cache, but not being unable to access it to install. With "mod_security" disabled it was possible to install without creating a backup first. Hope this helps. Regards, Hackasacka
  8. Hi Theo, We have been experiencing what appears to be exactly the same problem too. It works every time if you do not skip the backup. Of course this does mean you have to then manually remove the renamed folders and the backup. Just requesting our hosting provider disables "mod_security" as this can cause problems with "Processwire". Regards, Hackasacka
  9. Output Text Area Field (CK Editor) Additional Closing - P-Tag text-area field with CK Editor I don't think this exactly matches the problems discussed, but you certainly get an unexpected output in the front end code which may lead to some confusion. It was when proof reading the output code that I noticed some slightly strange behaviour when echoing the "text/area" field in an install v3.0.61 and validating the code. This practice allows an opportunity to catch any typos or other mistakes, like forgetting to close a "div" etc. It also helps to see how the browser parses and interprets the code too. A code editor also helps, but my human error still can cause a problem. As most web browsers show some validation in the source (typically ctrl+u) of the web page this is an easy way to have a quick look to see if all the nesting of html elements is correct or not. In doing this it was proving difficult to locate an erroneous " </p> " tag (potential errors usually show in red). Here is the Error:- There appears to be an additional closing P-tag if you enclose the text area output, such as the "$page->body" in a P-tag i.e. <p> <?= $page->body; ?> </p>. This is not good practice and the simple remedy when using CK Editor to parse the data in the text/area is to use a "<div>" or no element at all. Processwire rarely (if ever) errors, so it seems CK Editor may be the culprit for adding an unwanted closing P-Tag? Hope this helps.
×
×
  • Create New...