Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • @justinhill001

    I have a similar problem and after checking all other possibilities, I also came to the conclusion that the problem lies somewhere in the new theme release (probably the jQuery script responsible for the main navigation menu). This was confirmed when I replaced the latest version of twentyseventeen (3.5) with the older one (3.3).

    To do this confidently, efficiently and without interruption in the operation of the website, you can:
    1) download old version of twentyseventeen,
    a) 3.3 works great for me ,
    b) I grab it from https://themes.svn.www.ads-software.com/twentyseventeen/
    c) to get wole directry under windows you need SVN client like tortoise SVN
    2) to avoid identical names and complications when overwriting files on the computer, I temporarily change the name of the downloaded directory to the example “aaa”
    3) I upload the “aaa” directory with the the WP themes folder “/wp-content/themes” on serwer,
    a) after that I have there “twentyseventeen” directory with 3.5 version and “aaa” with 3.3 version;
    4) and now I want to switch them on WP, so under FTP client I need to…
    a) rename “twentyseventeen” to “whatever” (this way WP loose control over under 3.5 version of theme)
    b) and rename uploaded “aaa” to “twentyseventeen” (this way I replace previously lost 3.5 with older 3.3 version)
    c) if you make change names in poin 4 fast enough, none of the website visitors will even realize that you have done anything, and WP does not report any problem with such a change
    5) now all you need to do is: clear cache, refresh the page, and if your ploblem cause latest theme version, it should be gone :]
    6) BTW; turn off theme autoupdate function in WP, and do NOT update it manually till next version, couse you will once more at start point.

    Regards.

    edit:
    WP Rollback, could be good idea but I didn’t use it soI cant confirm how this will end. Im used to terminal commands, and not a fan of plugins experiments – it has a name, I suspect accurate is… to being an old dude :/

    Nevertheless, I keep my fingers crossed that hope everything goes smoothly and ends positively. Cheers

    • This reply was modified 9 months, 1 week ago by motkar.
    • This reply was modified 9 months, 1 week ago by motkar.

    give me a sec. Need to switch to PC couse my non english mobile change every word in post.

    @justinhill001 … Try to downgrade theme to 3.3 version.

    • Download 3.3 with svn (client)
    • upload it on serwer to themes directory under another name e.g. aaa
    • then under ftp switch themes dir names, change twen..7teen (v3.5) name to eg. temp and uploaded aaa (with v3.3) to twen..7teen
    • clear cache in browser and WP if you ar? using any plugin for it
    • check if that’s works

    Feels like there is a bug in main menu jQ in latest version so i my isue in your thread. I also nade all test, and eliminator plugin problem…

    Just wonder did anyone above is using 2017 theme, test how latest release works on mobile? Or just like to give good advices?

    • This reply was modified 9 months, 1 week ago by motkar.
    • This reply was modified 9 months, 1 week ago by motkar.
    • This reply was modified 9 months, 1 week ago by motkar.

    Also have problem with main navigation menu mobile devices and Twenty Seventeen v3.5 so I’m adding my report here instead of starting a new thread

    On desktop version everything works fine, menu also changes to mobile icon without problem, but then… I can’t click on it. Running website on mobiles have same results. Main menu icon is displayed but I can click/unwind it.

    I downgrade theme to 3.3 and everything works flawless.

    Same problem on Twenty Sixteen v3.1, and downgrade to 3.0 do the trick.

    If authors need more info, or see problem on working www. please drop a line. WP in multisite mode.

    • This reply was modified 9 months, 1 week ago by motkar.
    Thread Starter motkar

    (@motkar)

    Let me try explain.

    First, the problem:
    1) without SEOPress, title tag on divided into three parts with page break “Test” page, works like:
    a) first page: Test
    b) second page: Test – Page 2
    c) third page: Test – Page 3

    2) With SEOPress, and title code set to %%post_title%% | %%current_pagination%% I get:
    a) first page: Test |
    b) second page: Test |
    c) third page: Test |
    … so variable assigned to %%current_pagination%% is not passed, i suppose.

    3) I’ve also tried to set title code to %%post_title%% | %%page%%, and what I get in title was:
    a) first page: Test | 1 of 0 pages
    b) second page: Test | 1 of 0 pages
    c) third page: Test | 1 of 0 pages
    … so I knew that somewhere in the middle page numbers were not send at all to SEOPress.

    4) make some digging in template code, and find info that… title tag was left alone and operated only by WP build in functions. I tried to find a way to pass information about the current page directly from WP to SP tag.

    5) I used functions for %%page%% (it’s shorter, so easier to use), made a hook for it in template functions.php and add my code to it. Here it is

    function sp_context_paged($html)
    {
        $paged = (get_query_var('page'));
        if ($paged > 0) {
        return ":: page ".$paged;
        } else { return ""; }
    }
    add_filter('seopress_context_paged', 'sp_context_paged');

    it is crude and downright banal, but it does the job, fast and without any problems.

    6) Now I use %%post_title%% %%page%% in SEOPress title, and in title, and result in title is:
    a) first page: Test
    b) second page: Test :: page 2
    c) third page: Test :: page 3

    It takes me some time, so if you want use it please leave credits to motkar of psemu.pl

    Regards.

    Thread Starter motkar

    (@motkar)

    @johnzenausa

    well….
    1) first off all, thank you for replay, your work and plugin
    2) glad to hear about upcoming version with fix for reported problem.
    https://drive.google.com/drive/folders/19qnpRKkWbWHAQtokba8o1uNef3Zw23_Q?usp=sharing
    Here is my small contribution for next one.
    3) as for your question. Override plugin with old version results general crash, with white screen of death displayed both at frontend output and WP ACP. There was no other way but delete plugin to get WP up and running. (Re)Installing old version stops at plugin activation in plugins WP-ACP page with mentioned above “…syntax error, unexpected ‘function’ (T_FUNCTION)…” displayed in upper part of window.

    edit:
    4) everything works fine on 7.4.3 thank you

    with best regards /motkar

    • This reply was modified 4 years, 1 month ago by motkar.
Viewing 6 replies - 1 through 6 (of 6 total)