Bug 6082 – Problem while renaming custom blocks

Bug 6082 - Problem while renaming custom blocks

Summary:

Problem while renaming custom blocks

Status:	NEW

Product:	OJS
Classification:	Unclassified
Component:	Plug-ins
Version:	2.4.x
Platform:	PC Linux

Importance:	P3 normal
Assigned To:	PKP Support

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-10-29 04:27 PDT by jerico
Modified:	2012-09-21 13:14 PDT (History)
CC List:	5 users (show)

See Also:
Version Reported In:	2.3.3
Also Affects:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description jerico 2010-10-29 04:27:53 PDT

This issue was split off bug #6076.

The issue is that without IDs to reference in the plugin settings table, its not easy to rename the custom blocks. Try creating a new block from the Custom Block Manager, then adding content for that block (through the block's settings page). If you go back to the Custom Block Manager and change the name of the block, a new block will be created and the old one will disappear (though it still exists in the plugin_settings table, its no longer referenced in the row with plugin_name = customblockmanagerplugin and setting_name = blocks). I can spend some more time on this later, but it wasn't immediately obvious to me how to fix it.

Comment 1 Alec Smecher 2010-10-29 16:35:17 PDT

Rescheduling to 2.3.4; this is easily worked around.

Comment 2 vgabler 2011-04-19 08:37:32 PDT

James,

It seems that whatever work was done on this for the 2.3.4.0 release may have created another problem. Now the new custom block does not appear at all in the block plugins list in this version. I'll post a separate comment in the forum regarding this.

Thanks,