Forum Replies Created

Viewing 15 replies - 16 through 30 (of 40 total)
  • Thread Starter lucspe

    (@lucspe)

    Hi Daryll,

    Thanks for your reply, and for providing this plugin to the WordPress community.

    You wrote that the free version of the plugin does not add this functionality. Does the paid version add inline SVG support? I am asking because I looked on your site and it does not seem to mention that as one of the Pro features.

    As for using the IMG tag, that normally would be fine (and worked like a charm on other sites where I installed Safe SVG), but in this case the requirements would be to be able to do some CSS effects on the images, which could only be achieved by inlining the SVGs.

    Best,
    Luca

    Thread Starter lucspe

    (@lucspe)

    I understand your point of view about keeping things simple.

    However the point is that – as it stands – the plugin assumes that the footer text is hardcoded into “storefront_footer” action hook.

    I believe the use case of moving the footer text after the footer (so hooked into storefront_after_footer) is not uncommon and whilst this can be achieved manually by a developer, I think the overall concept of the plugin is to make managing footer credits easy on the end user.

    So it is not an “advanced or overly complicated” modification (as it just adds a select box in customizer so the user can choose whether to place the text in the footer or after) and would make this otherwise very useful plugin a bit more flexible πŸ™‚

    At any rate, case closed. Ultimately, this is your work so I respect your decision.

    I just would have preferred to avoid having to mantain a forked version of this for my sites, which is the reason why I approached you in the first place about this πŸ™‚

    Cheers,
    Luca

    Thread Starter lucspe

    (@lucspe)

    Ok, but you have not answered my question πŸ™‚

    How do I send you a pull request somehow?

    Thanks
    Luca

    Thread Starter lucspe

    (@lucspe)

    You’re welcome. I am glad that is useful.

    btw: I just wanted to mention that it is kind of standard practice (at least in my experience on patches I sent for other plugins) to give props in the changelog when you incorporate changes contributed by other people, even if – like in this case – is a small one πŸ™‚

    Cheers,
    Luca

    Thread Starter lucspe

    (@lucspe)

    Sure.

    I’ve sent you a pull request. I think that should be it.

    Thread Starter lucspe

    (@lucspe)

    Hi Christina,

    Sorry for the delay in answering, I was away for a few days.

    I have filled the contact form as requested.

    I was also wondering if – in the meantime – you guys have found out what the problem was, since it has been a few days and this seems to be a quite widespread issue.

    Thanks,
    Luca

    Thread Starter lucspe

    (@lucspe)

    Hi,

    To prevent a client or lower-level manager from making changes to the API key was exactly the case.

    Hiding those settings via CSS was my first thought however the TR in the form on the admin page doesn’t have a class assigned so having to rely on nth-child is a bit risky in terms of future-proofing it.

    I tried modifying the code in includes/class-settings.php to add CSS classes – as add_settings_field allows to pass that in the args array – however it seems that it is not supported by the framework used to add the settings. But I am not familiar with it so I might be missing something there.

    The option to force values via constants seems like a good workaround functionally, however it would have been best to be able to “visually remove” those fields.

    Thread Starter lucspe

    (@lucspe)

    Hi Christina,

    This happened both on PHP 5.5 (5.5.38) and PHP 7 (7.0.15)

    Cheers,
    Luca

    Hi Christian,

    I had the same issue (I actually came to this forum to post about that).

    What I found out is that upgrading to 3.3.6 seems to make BackWPup forget the FTP password.

    I went into the backup job, inserted the FTP credentials and saved. Now it is working for me.

    Thread Starter lucspe

    (@lucspe)

    Thanks!

    Hey,

    Just FYI I’ve encountered this issue before on non-english installs of WordPress. Try setting the date inputing it manually in the field and not with the datepicker (which would otherwise localize it).

    It works for me.

    Thread Starter lucspe

    (@lucspe)

    Hi thanks for the quick reply.

    Indeed it works as you described.

    However, I have a followup question.

    Given that the opening time is the same Mon-Fri, is there a way to avoid having a super-long list repeating the same information and shrink it up to simply “Mon-Fri” and then the time?
    Then next line “Sat-Sun” closed?

    I tried the show_opening_hours_brief=1 attribute however this way it shows as:

    Mo,Tu,We,Th,Fr 09:00 – 13:00; Mo,Tu,We,Th,Fr 14:30 – 18:30

    which is not very friendly to read.

    • This reply was modified 9 years, 6 months ago by lucspe.
    Thread Starter lucspe

    (@lucspe)

    Hi, thanks for the answer.

    As far as the free version on the WP repository, are you planning to still update it (at least for maintenance purposes, it states currently that is compatible up to WP 3.8.13 and it uses an older version of the Vegas background script) or is the plugin to be considered abandoned?

    Best,
    Luca

    Thread Starter lucspe

    (@lucspe)

    Hi,

    I see you have just released 1.2.34. Thank you for continuing the work on this excellent and free plugin.

    However – 1 month later from your initial reply – you still have not updated the github repo.

    As I said, that makes kind of difficult to keep forked versions updated, let it alone to contribute to the main development branch.

    Could you please clarify if you intend to continue supporting github or not? I really like your plugin but availability on github was a critical decision-making factor for me.

    Also it would be nice to consider for inclusion the pull request I sent you as I can imagine a number of use cases where users without admin priviledges would need to be given permission to manage the cookie settings options page….or at least close the pull request if you think it is not the case to include it πŸ™‚

    Thanks a lot and thanks again for this great plugin.

    Just wanted to post an update.

    In Firefox 36 (just released) the issue seems to be fixed (at least in my case).

Viewing 15 replies - 16 through 30 (of 40 total)