Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

6 Neutral

About rushy

  • Rank
    Jr. Member

Profile Information

  • Gender
  • Location
    Bournemouth & Málaga
  • Interests
    Motorcycles, music, meteorology, vintage radio restoration, computer chess programming, tech. in general

Recent Profile Visitors

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

  1. So far I found that using if(!$config->ajax): in my _main.php around head and foot parts and having a div targetted by Javascript as is commonly used - but in the case of an Ajax call I use wireRenderFile() to load markup from a file containing just the markup I need seems to work.... but I'm still playing with this. Paul
  2. Hello. I have recently adopted PW markup regions and really like this way of working. However, I am also trying to learn how to use Ajax and I am not sure of a good way to use the two together. Has anyone got any experience, tips or hints on using them together? For ajax - I've used a simple scheme where I have a "webservice" template and page that handles Ajax requests and returns the appropriate content wrapped with some markup for the requesting page. I have markup regions enabled and all my pages (bar webservice) include a _main.php which brings in the headers, a default body and the footer. My javascript intercepts the page links and does my ajax call to webservice and that sends back the appropriate markup which is then placed by in the div #body defined in _main.php. Does this seem a reasonable way to work? I guess I am looking for some advice before I invest too much time going the wrong way! Any guidance, remarks, comments, or a nudge in the right direction greatly appreciated. Paul
  3. Thanks for the suggestion. I couldn't see any errors in the Chrome developer network tab, but I did try adding the mod_security.c section as given in your other post. Unfortunately it didn't make any difference - the problem persists. I've installed Tracy debugger just in case it can throw any light on this problem. Now I have to learn how to use it properly! Rushy
  4. I'm using 3.0.98. I don't think it can be a PW problem though. I'm thinking perhaps server config? The fact is I've run the same build on a different server and the problem doesn't occur. Also it's fine on my local dev server. There are no errors seen to give me a clue (or I don't know where to look for config. errors)
  5. Good idea Robin, I will certainly try Tracy Debugger to see if it reports any problem in the backend. My $config is already set true and no visible errors are reported and everything else seems to work fine. Fingers crossed I can find something as I'm fresh out of ideas now...
  6. I tried the above to no avail. I'm really stumped now. Just can't get repeaters to work properly on this server but they are fine on another server. I can't see what the difference is...no errors or warnings. What a pain.
  7. I'm thinking this must be a PHP config. problem on the server. I found a problem with ini_set being disabled for security reasons and thought that would be the problem but now it's enabled the problem persists. See other post: override php.ini It's a long shot, but I think I will reinstall PW from scratch now that I have no server errors - just in case the installation had been affected by the PHP error. I wonder if there is a definitive statement of PHP functions that are required for correct operation of PW? That would help me track down the problem as I have no error messages anywhere now as far as I can see, but images in repeaters still don't work properly on this server. Paul
  8. No, I only have 2 'instances' of the repeater on my page, with 2 fields in the repeater 1 image and 1 TextareaLanguage. The image description field comes with the image.
  9. My problem seems specific to the description text fields provided with images. When used within repeaters, the description field is not saved and original text reappears after save. How can i enable extra logging to track down this problem? I have debug = true in config.php and no messages are seen. Any ideas of where to look? Thanks - Paul
  10. Thanks dragan. I have contacted the host support and they have changed the PHP config. to allow ini_set. The error in the error_log has now gone.
  11. Has anyone come across a shared server where the PHP function ini_set is disabled for security reasons? It seems to break PW correct operation and generate a large error_log. I keep getting guided toward adding lines into the vhost .htaccess but what exactly I should add is unclear. (I tried "php_flag php_admin_value on" and "php_flag php_admin_flag on" to no effect.) As far as I can see I do not have permission to change the php.ini. Anyway if anyone has solved this problem for PW sites on shared server I would be grateful of some help! More info for those that have time to read all about my investigations - I ran into the problem when I copied a site over to a clients shared server. The problem doesn't occur on my localhost or my own shared server, so I know it must be a config. problem on the clients host. The problem seems specific to text fields associated with images within repeaters. I have a repeater defined containing an image and if I change text in the description field and hit save - the text is not saved and original text reappears. This works fine on my local host and my shared host so I guess it something particular to the PHP config on my clients host. I have noticed on the client server there is an error_log in the public_html folder. It contained hundreds of the same error message - namely - [01-Nov-2018 13:49:42 Europe/Berlin] PHP Warning: ini_set() has been disabled for security reasons in /home/rushy/public_html/wire/core/ProcessWire.php on line 190 I don't see this error on the other servers, so guessing this is may an indication of the problem, I decided to try and find out how to re-enable ini_set on a shared server. There is quite a lot out there about this, but I've not found out a way so far. Thanks - Paul
  12. Thanks for the replies. I gave up on the profile export and did it all manually with a db dump as per bernhard suggested and it works fine. Robin S: I note the quote above and I had not fully taken that on board - I think my problems could have been due to not recreating the site user accounts and failure to setup the config.php correctly on the new server. Thanks to you both for helpful suggestions. Paul
  13. I'm trying to migrate a PW site on my local dev server to a shared hosted server and have used the ProcessExportProfile module to export a profile as a zip file. So far so good. I then deploy new install of PW on the server by unzipping the PW installation files but I do not run the install until I have replaced the various site profiles with the files from the exported profile. So basically: In the PW install files I delete all the site-* folders except site-default. This one I overwrite with the export profile folders so it contains my assets, install, modules and templates folders together with the exported config.php I then run the install in the browser in the normal way and it starts the installation and I can see my website profile in the list and I select it. It proceeds as normal and gets to setting up the database. I provide the db info. as usual and it proceeds as far the info. below and 'hangs' at this point , it never goes on to setup the PW login admin. and complete the install I am left at that screen. If I relaunch the browser at the site it all seems to work! BUT I have no admin login to PW so cannot get into the backend. I have basically followed the Installation, Moving and Troubleshooting guide by Joss Sanglier: http://processwire.com/docs/tutorials/installation-moving-and-troubleshooting/page4 Any idea where I could check for an error log or some help as I am at a loss as to the problem. Many thanks. Paul ProcessWire 3.x Installer Test Database and Save Configuration Database connection successful to pinpoin1_master Saved configuration to ./site/config.php Profile Import Imported database file: ./wire/core/install.sql Imported database file: ./site/install/install.sql
  14. Thanks for the heads up. Did you fix the problem? Hosting is provided by the client on a shared server so nothing special there and I don't have access to change anything like mod_security. I am getting an error_log file on the server filling up with "PHP Warning: ini_set() has been disabled for security reasons in /mypath/to/public_html/wire/core/ProcessWire.php on line 190". I don't get this on my localhost. The line at 190 is: ini_set('display_errors', true); so I think this is just to do with error reporting and probably not related to the problem, but I really don't know.
  15. Hi My first use of repeaters. They seem very useful, but I'm having a strange problem with the descriptions of the images field. I can't change them after deploying from my local dev server to the live server. I have defined a repeater with one images field and one textarea (multi language) field. This works as expected when added to a template and on the page I add an image and text in 3 languages. I usually populate the image description fields with a caption text in 3 languages so that I can output a caption if required under the image. Now this all works a treat on my test localhost server, but when deployed to the live site the captions cannot be changed on these repeater image fields. If I login to the live site and change the image text in there - as soon as I hit save the text goes back to what it was before! I am logged in as superuser so can't work out what the problem is. I had a search through the forums but couldn't find a similar problem. Any ideas where to look for some clues to what the problem may be? I'm using ProcessWire 3.0.96 Many thanks - Paul
  • Create New...