Dizkus

The new 760 uses PN in the database. My current 750 uses nuke.

These are for the prefix. Should I update the config.php to nuke instead before the upgrade?

Any easy way to fix this for the upgrade?

I am currently restoring my database.

Aight, i fixed it by changing my config.php to nuke for the prefix, then re upgraded.

I now have one issue that may be a bug.

Extra functions in the memberlist do not work do to a %20 instead of a underscore (_) That leads to module not found errors. can you point me to the right file to edit to fix this?

This %20 for spaces instead of _ also kills My egallery. You have to manually change the link in your browser for it to work. Does anyone have a fix for the Space issue?

You can alter the display name under administration-Modules->Edit (for the module you want). The problem with spaces in has been identified and a fix package will be available shortly (and isn't just spaces but other non-alpha numeric characters).

The use of the display name field is useful since rather than having module=My_eGallery you can simply call it gallery instead.

-Mark

That is so cool!!! thanks Mark, didn't know that option was there. It fixed it for the member list also by putting a _ between member and list. Did the same with the display name for myegallery.

Now once AutoTheme gets the new version out I'll be fully happy!...

Thanks again!

It's new in .760 and yes it's cool. But it also has practical uses for example in a non english install you can use the localized word for forum, gallery etc. as the module name. And your obviously not stuck with what ever the developer has decided on as the module name.

Note: This only works for API compliant modules i.e. those whose urls are index.php?module=<modname>.

-Mark</modname>

I had an oddity when i moved the site from 750 to 760. My table prefixes were nuke and i think still are. When i check my database i have a PN version and a nuke. is it ok to remove the PN, or are they linking them to the nuke prefix. my config.php has the prefix listed as nuke. I also noted after upgrading, via ftp, all the old modules were still there with the NS, plus the new ones. i had to delete some of the NS before theme functions like login would work (link still goes to the NS-USER) but somehow 760 redirects it where if the old NS-USER module was still in place, it would generate and error for me.

Hope this helps someone, and also i would like an answer to the prefix tables as it make my database pretty big.

The DEFAULT prefix in .760 is PN. This only applies to new installs. When upgrading whatever you have in config.php applies. As long as you follow the instructions then no pn_ tables should be created. Following the instructions should also mean you don't have the NS prefixed modules since the installation asks you to remove all files. You may find entries in your menu block/3rd party modules that refer to NS-* - these can be changed but the core does do an internal translation for you anyway so the link still work.

-Mark

Ahh ok. I am wondering... when i 1st installed it, i had a problem... didn't fully read the instructions and ran the installer. I restored my database from a dump, then re did it correctly. From what you are saying, i am assuming the PN ones can then be removed safely (i will make a backup 1st though) as since i had a nuke (not PN) prefixes, it uses them.