Forum Replies Created

Viewing 15 replies - 1 through 15 (of 131 total)
  • My hosting provider is bugging me to fix the XSS vulnerability issue in OSM.

    I have been a satisfied user of OSM for a long time.

    But if there is no fix I am going to have to look for a replacement plugin because I don’t want my hosting provider to shut my site down.

    I’ve been using this plugin very successfully but users using the Edge browser on desktops (Windows or Mac) have started seeing the “SmartScreen has blocked this unsafe content” red screen of death.
    This happens on some but not all my sites (all with the same hosting provider). Filling in the online feedback form hasn’t helped.
    Edge on my iPhone is OK and no other browser reports problems.

    You can see the problem at 2023 Spring Talks : Winchester Photographic Society (winphotosoc.uk)

    I have arranged that (for users of the Edge browser on desktop only) the same PDF is displayed using the Gutenberg File block which works fine.

    So there must be something about the code in this plugin which is susceptible to being treated as a scam.

    Thread Starter Adrian

    (@adriandw)

    Thank you.
    I thought I had already added those two lines into the wp-config.php file but there was one crucial mistake
    in my version I had included the web subdirectory in the path definition for the frontend and the backend.
    After I read your response and removed web from the front-end path definition in wp-config.php, LSCache Check is reporting hits for that site.
    Many thanks.

    Thread Starter Adrian

    (@adriandw)

    thanks – that’s helpful.

    A follow-up question:

    On the wordpress.com Account Settings page, how can I delete a self-hosted site?
    It’s currently the primary and only site connected to the account.

    Obviously I can delete it by closing the account, but is there another option?

    Thread Starter Adrian

    (@adriandw)

    This problem (of continual refreshing the preview) has stopped. I don’t know what caused or why it cleared.

    But I still think there should be the option to revert to the previous behaviour, to update the preview on request only.

    **sorry – I missed the checkbox in the settings page and I have only just seen your post with details about disabling the Live Preview. ***

    • This reply was modified 2 years, 11 months ago by Adrian.
    Thread Starter Adrian

    (@adriandw)

    @munirkamal
    Version 1.33.0 has fixed the problem that logged-in admin users could not view WP Cloud galleries on the front end.

    But I am seeing another problem, with the new Live Preview.
    When I try to preview a using the Live Preview, it gets into a loop of continually saving the draft and refreshing the live preview screen.
    If you close the live preview tab, it continues to save and resave the draft.
    The only way to stop this is to close the edit window and reopen it.

    This on my live site which is using the Customizr Pro theme, but does not happen on my development site which is using the Kadence theme.

    Is there a way to disable the Live Preview and revert to the old preview?
    Live preview could be a nice idea in some cases but if you are making a lot of changes it could be expensive in performance terms.

    Thread Starter Adrian

    (@adriandw)

    Hi @munirkamal
    Thank you very much for your quick response.

    My first tests show that the problem is fixed.

    Everything should be OK now, but if I do find any problems in further testing, I’ll let you know.

    Adrian

    Adrian

    (@adriandw)

    Another problem with the block editor crawling.
    Kadence Theme with Pro Extensions, WordPress 5.8.2

    After selectively deactivating and reactivating plugins I found what appears to be a conflict between EditorsKit and Real Media Library.

    When both of those plugins are activated, the editor crawls.
    When I deactivate either one of them, the editor works normally.

    I haven’t tried selectively disabling components of EditorsKit

    • This reply was modified 3 years ago by Adrian.
    Thread Starter Adrian

    (@adriandw)

    Thanks for the update.
    My (not yet final) version using OpenLayers is at
    https://comptonshawford-pc.gov.uk/WorkInProgress.html
    As I can create polygons, I can use co-ordinate pairs and don’t need to imbed KML.
    I will probably imbed it in WordPress using an iframe.
    If you put raw html in a WordPress page, there’s always the chance that the WordPress editor will mangle it.

    From my point of view, if you enable layers, it will make the plugin hugely more useful.

    I was wondering whether to switch to Leaflet, but OpenLayers seemed the easiest route starting from the OpenSpace API.

    Thread Starter Adrian

    (@adriandw)

    With the aid of the examples on the OpenSpace migration pages I’ve figured out how to get the OpenLayers layer switcher control working.
    So I’m now confident I can migrate successfully to OS DataHub.

    From the point of view of future maintenance I’d have preferred to drop the bespoke javascript code I developed for the OpenSpace API and use your plugin, because it has many nice features.

    But without layer switching, the option to load multiple gpx/kml files preserving colour settings, I’ll stick with my roll-your-own code for now.

    Thread Starter Adrian

    (@adriandw)

    Many thanks for your prompt response.
    I use KML because it supports polygons which I don’t think are possible with a GPX.

    One of the main users of the boundary maps on our parish website is the local school. As a CofE school it’s allowed to use the ecclesiastical parish boundary to define its catchment area, which comes into play over prioritising admissions. Disappointed parents can escalate an appeal, so the school needs to know it’s on firm ground. I don’t believe there’s any other website which makes it as easy to compare the various boundaries as my (OpenSpace) map at https://comptonshawford-pc.gov.uk/about/maps/parish-boundary/

    And talking about walkers, this map https://comptonshawford-pc.gov.uk/TwoRoutes2.html shows two overlapping circular walks in different layers which you can toggle on and off.
    This also has to be converted or sunsetted.

    Thread Starter Adrian

    (@adriandw)

    Thank you, you’re correct.
    Excel is trying to be too smart.
    I think it recognises the Updated Date field as a date and reformats it to dd/mm/yyyy on input.
    Then if I make changes to the file and resave, the Updated Date field exports as dd/mm/yyyy, which confuses the Link Library import process.

    LibreOffice and OpenOffice and the TextMate text editor on my Mac preserve the format of the Updated Date field.

    (I should have remembered that I had a problem before with Excel messing up the format of dates in a csv file.)

    Thank you for your help. If I go ahead and put Link Library into production I will certainly consider making a donation.

    If you export to PDF from Open Office, you can choose the initial view when the PDF is opened.
    If you have a PDF editing tool Some PDF editors (including PDF Studio, Acrobat) let you change the initial view that was set when the PDF was created.
    I often use that to set the initial view to be page+bookmarks.

    If you have done that, then the PDF.js viewer respects the initial view setting. It will display the table of contents if that was what you set as the initial view.

    @jelmerjellema
    It turns out the problem was still there – it just wasn’t showing me the error message in real-time.
    But I received an email from WordPress

    Your Site is Experiencing a Technical Issue
    WordPress caught an error with one of your plugins, MailPoet 2.

    So I applied your fix to render_engine.php and the problem went away.
    Thank you again

    Adrian

    Thank you @jelmerjellema, that’s good to know.

    I had been running my site on 7.2 to avoid the problem, so I just updated to 7.3 in preparation to apply your fix.

    The level of PHP 7.3 available from my hosting provider is now 7.3.7.

    And I have been unable to recreate the problem.
    Is it possible this was recognised as a compatibility bug in PHP 7.3 and is now fixed in 7.3.7? It wasn’t clear from the changelog at https://www.php.net/ChangeLog-7.php#PHP_7_3

    Adrian

Viewing 15 replies - 1 through 15 (of 131 total)