Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter vandazocca

    (@vandazocca)

    Hi Bryle,
    Yes, the files are still on my Google Drive.
    As you mentioned, I updated the backup list with “rescan remote storage”.
    The result was not what I expected, it contained other backups, let me explain:

    I use my Google Drive map UpdraftPlus for 4 websites. For every website I would like to use a separate folder, but this is not possible with the free version of UpdraftPlus.
    For every site I keep 4 backups. So there are 80 files in my Google drive (4 websites x 4 backups for every website x 5 files every backup).
    After updating the backup list with “rescan remote storage”, the last 4 backups (4×5 = 20 files) are put in UpdraftPlus desktop of the current website. These 4 backups are not the backups of the current website, these 4 backups are the last backups of all the 4 websites. Apparently, UpdraftPlus cannot select the backups of the current website from Google Drive. The risk of the “rescan remote storage” operation of UpdraftPlus is thus confusing backups of another site. I have to restore the correct backups manually.

    Remains that the problem of not finding the file is still there. After updating the backup list, the Download of the Database backup of 2021-01-30-2323_Mondhyginiste_Annette_Derx still return the same error as mentioned in above issue. The other 19 files are OK.

    I encounter the same problem for a website of a friend that uses his own Google Drive storage for a single website backup. If it helps I can send the log (if you tell me how to post this file).

    Regards,
    Vanda

    Thread Starter vandazocca

    (@vandazocca)

    Hi Bryle, Yes I use version 1.16.47. I think the backup of 01/30/2021 was done with an earlier version.
    Regards,
    Vanda

    Thread Starter vandazocca

    (@vandazocca)

    You are great! Thank you

    Thread Starter vandazocca

    (@vandazocca)

    Because I didn’t t see the 2 options, I thought they didn’t work.
    Does this mean that I can’t control the two hidden options anymore?
    What are the settings of the 2 hidden options right now?
    How does a user know of these options, if they are hidden?

    Regards,
    Vanda

    I have the same problem with 2 websites after updating Elementor today.
    I have another website that works ok. I did not update Elementor for this website.

    Thread Starter vandazocca

    (@vandazocca)

    Thank you Takayuki, I look forward to the update.

    Thread Starter vandazocca

    (@vandazocca)

    Thank you Roman for your answer.

    I am very pleased to hear that you will continue to support the OLD solution for existing users. That gives me more time to figure out how to convert to Elementor and use of custom-post-types. I am very charmed by the usability of Elementor!

    I would like to give some suggestions for changes to Sydney that you could consider when using Elementor and custom-post-types. I think they would be a benefit for all users.

    1. To avoid confusion, change the name of the version of the ‘Sydney Toolbox’ plugin that works with Elementor, because the functionality of this plugin differs from the functionality of the original ‘Sydney Toolbox’ plugin. A suggestion: Sydney elements for Elementor.

    2. Add a new element to the new version of ‘Sydney Toolbox’ for Elementor that can handle custom-post-types. In this element add the following functionality: choose the custom-post-type to be displayed; choose which categories of this custom-post-type must be displayed (all, one or some); choose if the filter of the selected categories must be displayed and if so specify the order of the categories in the filter and give the name for All; choose number of columns for displaying the feature images; choose the format of the images; choose gridstyle (boxes or masonry); choose number of posts to be displayed, or all; display the filter, if requested, and the feature images with title of the number of posts of the selected custom-post-type and categories in the desired format and gridstyle.

    3. Making new custom-post-types can be done with ‘Custom post type UI’ plugin. For the existing custom-post-types (especially the projects pages) it would be nice if they are not lost after installing Elementor. I do not know if this is possible. I found the ‘Post Type Switcher’ Plugin which can shift a page of a post type to another post type. This is perhaps the solution to save the projects pages to a new custom-post-type before installing Elementor. I will investigate this in the future. Anyway, it would be nice for users of Sydney to see an instruction how to switch from Page Builder by SiteOrigin to Elementor.

    I hope we will see (some of) these suggestions, when feasible, realized in the future.
    Kind regards,
    Vanda Zocca

    Thread Starter vandazocca

    (@vandazocca)

    Thank you Roman for the quick response.

    I think that the NEW solution requires a lot of rework for existing websites that use the OLD solution and have already a lot of Projects pages created in Project custom-post-type. The NEW solution is also not so flexible as the OLD one.

    With OLD and NEW solution I mean:

    OLD Solution: ‘Sydney’ theme, ‘Sydney Toolbox’ old version with widgets like ‘Sydney FP: Portfolio’, with ‘Page Builder by SiteOrigin’ and with a lot of Projects pages created in Project custom-post-type.

    NEW Solution: ‘Sydney’ theme, ‘Sydney Toolbox’ new version with elements like ‘athemes: Portfolio’ and the Page Builder ‘Elementor’.

    The first consequence of the NEW solution is that before installing Elementor you have to figure out how to save the existing Projects pages because they will disappear after installing Elementor. I still have to figure out how to do this. I hope that there is a solution other than manually rebuilding every Project page. Suggestion welcome! If I keep using ‘Page Builder by SiteOrigin’, will the old version of ‘Sydney Toolbox’ with widgets like ‘Sydney FP: Portfolio’ still work?

    The second consequence is that the NEW solution does not support custom-post-types whereas the OLD solution did. It is good practice to separate Projects pages from Standard WordPress pages when there are a lot of Projects that contain more information than only an single image and you want to categorize them by categories/sub-categories.

    The third consequence is that the NEW solution does not automatically updates Portfolio pages. With the OLD solution you could create one or more Portfolio pages that displays the Projects of certain categories/subcategories. You only had to add the categories to the widget ‘Sydney FP: Portfolio’ of the Projects you wanted to display. When new Projects where added, they where automatically put on the Portfolio pages with corresponding category/subcategory. With the NEW solution you have to change every time the Portfolio pages when adding a new Project: add image, url and filter term. There is no more a relation between the title, image and category/subcategory used in the Project page with the title, image, filter term used in ‘athemes: Portfolio’ element. You have to maintain all this manually.

    So, I can upgrade the website with a lot of rework and then, each time a project is added, manually update the portfolio pages. But that is very laborious. That is why I asked if there will be a better solution for this in the near future. I truly hope so.

    Kind regards,
    Vanda Zocca

Viewing 8 replies - 1 through 8 (of 8 total)