Jump to content

Woodsman

Clients
  • Posts

    2,445
  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by Woodsman

  1. On Friday, September 25, 2015 12:37:01, mark007 said:

    During the upgrade process form 3.4.7 to the latest 4.x Version I'll got very often a 403 Forbidden error. Did anyone know whats the reason or how I can solve this problem? Normally I had to refresh the site in order to proceed.

    A 403 error is usually the page can't be displayed at the time. If a refresh does not work immediately try a hard refresh Ctrl-Alt-Delete and see if that works for you.

  2. 2 hours ago, media said:

    Hi guys,

    I have one question what happens to your mods you do not have an upgrade or it is discontinued (you do not have an upgrade for them)?

    Do they stay in the database or system wipe them off????

    Second question: Is it possible to translate the script before upgrade??? If yes, where is the lang file? and what is the procedure?
    Thanks

    As Wim explained you can do either or - delete or disable 3rd party applications. Deleting you may run into a chance of fragments hanging around it your database that you will have to manually remove prior to the upgrade. This I won't recommend to anyone without database experience. The preferred method is by disabling the 3rd party applications in the ACP - Applications & Modules - Manage Applications & Modules and then  disable 3rd party hooks via Manage Hooks just below. This will allow the 4.0 upgrade to bypass those disabled applications and hooks.

    In your new upgraded 4.0 test site  ACP - System - System Features - Applications, at the very bottom it will show all your disabled files. These I would keep as they are for now just in case they get updated by the developers.

    Happy Upgrading!

  3. 3 hours ago, media said:

    Hi Woodsman,

    Thank you for the explanation, at the beginning of this topic you guys were talking about beta a lot and that just made me think that this topic is about beta version of IPB upgrade....

    Anyway, after you post and EarthDog post I went back and read the topic and see what you guys are talking about....

    Thank you for your help

    I'm glad to help. Fear of the unknown gets to the heart of the majority. But then we soon realize there was nothing to fear.....

  4. Well thankfully I backed up the first IPS4 upgrade MySQL DB and I just simply copied the two tables that I had the issues with (ips_core_notifications and ips_downloads_reviews) and the upgrade script went through without an issue. Also the theme issue has completely gone! Whether this was because of removing the plugins first or because I was using the newly patched IPS4 build I don't know, but my site is now back online and working. :)

    At this point it is hard to say which fixed it for you but I am glad to hear it is working. On the other hand I ran the upgrade on an un touched forum backup on my local and again trashed it. Same upgrade with all the 3rd party products disabled or removed and now a working  4.0.13.1 test site added to my collection...

    My personal hunch is for most people @Stuart Silvester may be correct in most common situations it may work as intended. In my situation I merged another site with my own back in 2012 that caused a big issue with the merge where the conversion tool needed some serious attention and rebuilding from the ground up in order to get the two sites to come together and work properly. Because of this I now feel my merged site still has a few underlying issues that will cause the upgrade problems as I am seeing them on my local. Is this situation the cause of my upgrades? That too is hard to say for sure. But I can honestly say that the upgrade (In my case) will fail every time without going through all the steps mentioned in this article. Yes it is time consuming, but then again a little extra time spent is worth the sanity loss.

  5. That really isn't required, anyone following this instruction will permanently delete any data stored by those 3rd party applications and be unable to upgrade to their IPS4 version. The upgrade process will remove any 3.x themes and plugins.

    This has been the recommended method from the beginning from the previews through betas. The reason for following this is to do just that. Remove all unwanted threats of instability from the previous versions.

    This is the only method I have been able to upgrade without error and I have made over 20 plus upgraded test sites on my local that were perfectly sound. Those that I let slide without manually cleaning most all failed before the upgrades were completed. And let me tell you I hate those red error bars that popped up caused by 3.4.x 3rd party themes and mods. Those that I took the time with and utilized the above process worked as they should even with a good 80% of the bugs that showed up in the tracker I was having very little issue with.

    Every fresh install (no upgrade) worked fine.

  6. When I install IPS4 fresh everything works perfectly with no issues at all. However during an upgrade from IPB3.4.7 it removes the old themes and defaults to the IPS4 default theme. However for some reason this doesn't seem to work. I have also tried installing a few of the free IPS4 themes and setting those to default as well as setting it so all users use it without luck too.

    It's a very strange issue that I and I guess many others can't explain. Some people have managed to get it working after the Support -> Problem Option -> Clear Cache stage but it seems like this doesn't always work (and doesn't with me).

    In preparation of the 3.4.x files it is best to manually remove all third party skin themes, mods, hooks and applications before proceeding to the upgrade.

    It sounds as though you have fragment hanging around during and after the upgrade. When you do a fresh install there is nothing to convert so therefore nothing to be missed during its cleanup...

    Try another upgrade. But first manually remove all third party skin themes, mods, hooks and applications as explained in this topic.

  7. Ha anyone found a solution to the "css/lack of theme" issue after upgrading to IPS4?

    If you are trying to use the 3.4.x themes they wont work. Nor will any of the mods & apps. 4.0 is a totally different animal.  You would have known this by fully reading the topic not to mention it has been stated many of times in this topic and others. Now if I misread your comment as a wise ass I apologize. But that's the way I am reading it.

     

    @Woodsman : Maybe you should add directory ccs_files that has to be kept and copied over when you clean upgrade along with public,screenshots,downloads e.t.c.

    Or it has moved elsewhere?

    All the pertinent files and directories that need to be edited and copied over are mentioned. 

  8. https://docs.moodle.org/23/en/Converting_your_MySQL_database_to_UTF8

    This explains it in full, I used the commands needed from here, then you have to make sure to change all instances of the current charset to UTF8 with something like vim or nano. After that, reimport the dumped DB, and try running the upgrader again, and it shouldn't ask you to convert anymore. Your forum will go down with this change though, so I recommend that you make proper notices when doing so.

    This honestly can be done for any charset of any kind, and if the converter is doing weird stuff from the beginning, I suggest you ditch it and use this instead.

    Nice-

    I am sure those having trouble converting or issues with the converter itself will find that there is another alternative to getting it to play nice.

  9.  

    Just a heads up, I got the upgrade to work! I needed to convert the char. set via mysql dump instead, the current converter doesn't work at all.

    When you have the chance post your method here for those having the same issue. I think it will save a few strands of hair being ripped out

    Though the converter did a great job for a number of us there are still those like yourself getting frustrated with it not working for them.

  10. I have used the converter both ways on a few of test sites on my local without issue. Both are working fine on my local. My live 3.4.8 site is also utf-8mb4 and it too is working as expected.

    Remember that the utf-8 is more of a common character standard as where utf-8mb4 is more complex for other applications.

  11. Are you lookig to upgrade your live board or a test board?

    IPS will upgrade your licensed live board for free as far as the core and official apps you hold license to. Just go to your clients center and submit a ticket.

    Unfortunatly they will not be able to upgrade your 3rd party apps. These you will need to contact the app authors.

  12. Hello Sir

    I have made 3-4 custom app..costed me thousand of dollars. So any developer can convert that to ipboard 4 or i have to contact only who have made it? And will they charge only for converting or making whole app?

     

    What i want to ask, is making ipboard 4 app/hook by seeing code of 3.4 app/hook is easy or they need to make it from start.

    First Part

    Again - The framework IPS 4.0 is built on is not compatible with any part of the older 3.4.x or earlier structures. This has been stated a number of times in this topic as many other topics. Skin Themes, Mods, apps and hooks from the previous versions can not be used with 4.0's new frame work. All of these have to be rebuilt from the ground up using the new framework.

    2nd Part

    Yes  it is possible for the coder (understanding the 4.0 framework) to rewrite a hook compatible to IPS 4.0.

     

     

×
×
  • Create New...