Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

Coleen_Astalos
This afternoon I noticed that my customizations I've made to Nabble (that have been working for years) were not working.  Went into the NAML editor and get the error messages below.

I haven't changed anything on my site, so it must be something on the Nabble end.  I need this resolved ASAP as it's causing post emails to be sent out to non-members (because I have a customization to only send the emails if the user is in a particular user group).  I'm sure I'll start to get complaints very quickly.  
Thanks,
Coleen

Error
macro or method for 'report_inappropriate_content_panel' not found in [basic, nabble, servlet, classic_view_namespace, forum_topic_namespace, node_page, html] stack = [basic, nabble, servlet, classic_view_namespace, forum_topic_namespace, node, node_poll, node_page, html]
in report_inappropriate_content_panel(custom_tweak:topic_html:31) -
in body(nabble:topic.naml:146) -
in body(nabble:utilities.naml:10) -
in body(responsive:responsive.naml:13) -
in nabble_html(responsive:responsive.naml:9) - - public void nabble.view.web.template.ServletNamespace.nabble_html(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.ScopedInterpreter)
in html_impl(nabble:utilities.naml:4) -
in html(nabble:topic.naml:141) -
in do(nabble:utilities.naml:970) -
in as_node_page(nabble:utilities.naml:970) - - public void nabble.view.web.template.NodeNamespace.as_node_page(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.ScopedInterpreter)
in do(nabble:utilities.naml:975) -
in get_node_from_request_parameter(nabble:utilities.naml:975) - - public void nabble.view.web.template.ServletNamespace.get_node_from_request_parameter(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.ScopedInterpreter) throws java.io.IOException,javax.servlet.ServletException,nabble.naml.namespaces.TemplateException
in catch_exception(nabble:utilities.naml:974) - - public void nabble.naml.namespaces.BasicNamespace.catch_exception(nabble.naml.compiler.IPrintWriter,nabble.naml.compiler.Interpreter)
in get_node_from_parameter(nabble:utilities.naml:970) -
in node_page(nabble:topic.naml:138) -
in topic_min_html(custom_tweak:topic_html:2) -
in topic_html(nabble:topic.naml:59) -
in topic_html_page(nabble:topic.naml:46) -
in do(nabble:topic.naml:28) -
in forum_topic_namespace(nabble:topic.naml:46) -
in do(nabble:topic.naml:29) -
in classic_view_namespace(nabble:topic.naml:46) -
in (nabble:topic.naml:45) -
Full Stack Trace
nabble.naml.compiler.Compiler.getCommandCall(Compiler.java:978)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:521)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.getMacroArgChunk(Compiler.java:634)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:510)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.getMacroArgChunk(Compiler.java:634)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:510)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.getMacroArgChunk(Compiler.java:634)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:510)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.getTagArgs(Compiler.java:769)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:533)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.compileMacro(Compiler.java:240)
nabble.naml.compiler.Compiler.getMacroChunk2(Compiler.java:729)
nabble.naml.compiler.Compiler.getMacroChunk(Compiler.java:660)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:525)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.compileMacro(Compiler.java:240)
nabble.naml.compiler.Compiler.getMacroChunk2(Compiler.java:729)
nabble.naml.compiler.Compiler.getMacroChunk(Compiler.java:660)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:525)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.getMacroArgChunk(Compiler.java:634)
nabble.naml.compiler.Compiler.multiMethodTag(Compiler.java:550)
nabble.naml.compiler.Compiler.multiMethodTag(Compiler.java:593)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:495)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.getMacroArgChunk(Compiler.java:634)
nabble.naml.compiler.Compiler.multiMethodTag(Compiler.java:550)
nabble.naml.compiler.Compiler.multiMethodTag(Compiler.java:593)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:495)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.getDotArg(Compiler.java:740)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:531)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.compileMacro(Compiler.java:240)
nabble.naml.compiler.Compiler.getMacroChunk2(Compiler.java:729)
nabble.naml.compiler.Compiler.multiMethodTag(Compiler.java:584)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:495)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.compileMacro(Compiler.java:240)
nabble.naml.compiler.Compiler.getMacroChunk2(Compiler.java:729)
nabble.naml.compiler.Compiler.getMacroChunk(Compiler.java:660)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:525)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.compileMacro(Compiler.java:240)
nabble.naml.compiler.Compiler.getMacroChunk2(Compiler.java:729)
nabble.naml.compiler.Compiler.getMacroChunk(Compiler.java:660)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:525)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.compileMacro(Compiler.java:240)
nabble.naml.compiler.Compiler.getMacroChunk2(Compiler.java:729)
nabble.naml.compiler.Compiler.getMacroChunk(Compiler.java:660)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:525)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.compileMacro(Compiler.java:240)
nabble.naml.compiler.Compiler.getMacroChunk2(Compiler.java:729)
nabble.naml.compiler.Compiler.getMacroChunk(Compiler.java:660)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:525)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.getMacroArgChunk(Compiler.java:634)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:510)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.compileMacro(Compiler.java:240)
nabble.naml.compiler.Compiler.getMacroChunk2(Compiler.java:729)
nabble.naml.compiler.Compiler.multiMethodTag(Compiler.java:584)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:495)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.getMacroArgChunk(Compiler.java:634)
nabble.naml.compiler.Compiler.singleMethodTag(Compiler.java:510)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:493)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.compileMacro(Compiler.java:240)
nabble.naml.compiler.Compiler.getMacroChunk2(Compiler.java:729)
nabble.naml.compiler.Compiler.multiMethodTag(Compiler.java:584)
nabble.naml.compiler.Compiler.compileElement(Compiler.java:495)
nabble.naml.compiler.Compiler.compile(Compiler.java:303)
nabble.naml.compiler.Compiler.compileMacro(Compiler.java:240)
nabble.naml.compiler.Compiler.compile(Compiler.java:86)
nabble.naml.compiler.Compiler.compile(Compiler.java:58)
nabble.naml.compiler.Program$1.get(Program.java:88)
nabble.naml.compiler.Program$1.get(Program.java:84)
fschmidt.util.java.Memoizer$1.call(Memoizer.java:30)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
fschmidt.util.java.FastFuture.run(FastFuture.java:21)
fschmidt.util.java.Memoizer.get(Memoizer.java:37)
nabble.naml.compiler.Program.getTemplate(Program.java:280)
nabble.naml.compiler.Compiler$Subroutine.run(Compiler.java:1755)
nabble.naml.compiler.BlockWrapper.printTo(BlockWrapper.java:68)
nabble.naml.compiler.TemplatePrintWriter.print(TemplatePrintWriter.java:22)
nabble.naml.namespaces.BasicNamespace$SwitchNamespace._case(BasicNamespace.java:901)
sun.reflect.GeneratedMethodAccessor130.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
nabble.naml.compiler.JavaCall.invoke(JavaCall.java:26)
nabble.naml.compiler.Compiler$Block.invoke(Compiler.java:1557)
nabble.naml.compiler.Compiler$Block.run(Compiler.java:1631)
nabble.naml.compiler.Compiler$Chunks.run(Compiler.java:1121)
nabble.naml.compiler.BlockWrapper.printTo(BlockWrapper.java:68)
nabble.naml.compiler.ScopedInterpreterImpl$1.printTo(ScopedInterpreterImpl.java:25)
nabble.naml.compiler.TemplatePrintWriter.print(TemplatePrintWriter.java:22)
nabble.naml.namespaces.BasicNamespace._switch(BasicNamespace.java:872)
sun.reflect.GeneratedMethodAccessor177.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
nabble.naml.compiler.JavaCall.invoke(JavaCall.java:26)
nabble.naml.compiler.Compiler$Block.invoke(Compiler.java:1557)
nabble.naml.compiler.Compiler$Block.run(Compiler.java:1631)
nabble.naml.compiler.BlockWrapper.printTo(BlockWrapper.java:68)
nabble.naml.compiler.TemplatePrintWriter.print(TemplatePrintWriter.java:22)
nabble.naml.namespaces.BasicNamespace._if(BasicNamespace.java:140)
sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
nabble.naml.compiler.JavaCall.invoke(JavaCall.java:26)
nabble.naml.compiler.Compiler$Block.invoke(Compiler.java:1557)
nabble.naml.compiler.Compiler$Block.run(Compiler.java:1631)
nabble.naml.compiler.Template.run(Template.java:61)
nabble.naml.compiler.Template.run(Template.java:33)
nabble.modules.ModuleManager.run(ModuleManager.java:265)
nabble.view.web.template.NamlServlet.service(NamlServlet.java:165)
nabble.view.web.template.NamlServlet.service(NamlServlet.java:134)
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
fschmidt.util.servlet.JtpContextServlet.service2(JtpContextServlet.java:461)
fschmidt.util.servlet.JtpContextServlet.service(JtpContextServlet.java:332)
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:565)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1360)
org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:77)
org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:144)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331)
cachingfilter.CachingFilter.doFilter(CachingFilter.java:135)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331)
fschmidt.util.servlet.BadBotFilter.doFilter(BadBotFilter.java:74)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331)
fschmidt.util.servlet.ConnectionLimitFilter.doFilter(ConnectionLimitFilter.java:94)
nabble.view.lib.NabbleConnectionLimitFilter.doFilter(NabbleConnectionLimitFilter.java:26)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331)
nabble.view.lib.NabbleErrorFilter.doFilter(NabbleErrorFilter.java:21)
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1331)
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:477)
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1031)
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:406)
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:965)
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
org.eclipse.jetty.server.Server.handle(Server.java:349)
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:449)
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:910)
org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:634)
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230)
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:76)
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:609)
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:45)
nabble.model.Executors$1$1.run(Executors.java:27)
fschmidt.util.executor.ThreadTimer$1.run(ThreadTimer.java:18)
fschmidt.util.executor.AbstractThreadPool$1.run(AbstractThreadPool.java:29)
java.lang.Thread.run(Thread.java:748)


Reply | Threaded
Open this post in threaded view
|

Re: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

Coleen_Astalos
Is there ANYTHING I can do to get this error fixed?  Paid support????  
I'm getting LOTS of emails from past members wanting to know why they're getting emails all of the sudden.  Is there a way if I give you a list of email addresses that you can unsubscribed them from the entire forum so at least those that are complaining stop getting the messages?  Until you can get it fixed?
I need to get this fixed ASAP!
Thanks,
Coleen
Reply | Threaded
Open this post in threaded view
|

Re: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

Coleen_Astalos
I figured out a way to patch this until you get it fixed.  Since it was complaining about not being able to find "report_inappropriate_content_panel" macro, I created a macro under my customizations by that name with nothing in it.   This will PATCH me until you can fix it.

I would also like to understand how you're working on changes, it seems that you should have a test site that you test changes on before rolling them out to the main site.  So that you know they are working/functional.  I need to have a stable system for my 800+ members and not have unexpected errors come up like this.

Thanks,
Coleen
Reply | Threaded
Open this post in threaded view
|

Re: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

Coleen_Astalos
On further investigation, I discovered that it looks like you removed this functionality (report_inappropriate_content_panel) and since the call to it was in topics_html which I had customized, I still had to call to it.  

I have quite a number of customizations on my site.  Is there a way when you're updating modules that you can put out a list of updated modules so I can compare them to my list of customizations and roll those modifications into my customizations?   This would avoid a situation like this in the future.

Thanks,
Coleen
Reply | Threaded
Open this post in threaded view
|

Re: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

Franklin <Nabble>
Administrator
Coleen_Astalos wrote
I have quite a number of customizations on my site.  Is there a way when you're updating modules that you can put out a list of updated modules so I can compare them to my list of customizations and roll those modifications into my customizations?   This would avoid a situation like this in the future.
This is a good idea.  I will post changes here in the future.  But most changes should end by the end of this week.
Reply | Threaded
Open this post in threaded view
|

RE: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

Coleen_Astalos

Franklin,

How about creating a Change Log forum under the support topic and posting them there?  That would allow the change history to be all in one place (and allow people to subscribe to just get the change history via email). 

 

I'm curious what kinds of changes you have in the works.  We're a pretty heavy user of Nabble and would be happy to collaborate on changes that might improve the overall features & benefits of Nabble.   

 

So far Nabble is unique in its ability to be able to send the forum posts, in entirety, to the users that have subscribed for email - as well as being able to post via email (basically interact completely via email, if desired).  Plus I love that Nabble is mostly open source and allows me to customize many of the features to fit our needs. 

 

The one major shortfall that I hope doesn't lead to the demise of Nabble is the ability to run on SSL.  With the ever increasing security concerns on the internet as well as updated browser warnings for sites that are not running securely, becoming SSL complaint should be high on the priority list. 

 

Thanks for all you do!

Coleen

 

 

From: Franklin <Nabble> [via Nabble Support] [mailto:[hidden email]]
Sent: Tuesday, September 19, 2017 11:50 AM
To: Coleen_Astalos
Subject: Re: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

 

Coleen_Astalos wrote

I have quite a number of customizations on my site.  Is there a way when you're updating modules that you can put out a list of updated modules so I can compare them to my list of customizations and roll those modifications into my customizations?   This would avoid a situation like this in the future.

This is a good idea.  I will post changes here in the future.  But most changes should end by the end of this week.


To unsubscribe from Nabble Error - macro or method for 'report_inappropriate_content_panel' not found, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

Franklin <Nabble>
Administrator
Coleen_Astalos wrote
How about creating a Change Log forum under the support topic and posting
them there?  That would allow the change history to be all in one place (and
allow people to subscribe to just get the change history via email).  
There won't be many changes, so I am just using a thread for this.  You can subscribe to the thread.
 
I'm curious what kinds of changes you have in the works.  We're a pretty
heavy user of Nabble and would be happy to collaborate on changes that might
improve the overall features & benefits of Nabble.  
Right now I am just trying to make Nabble stable enough to that I can then work on other things like Blasma.  This mostly involves removing features that cause trouble.

So far Nabble is unique in its ability to be able to send the forum posts,
in entirety, to the users that have subscribed for email - as well as being
able to post via email (basically interact completely via email, if
desired).  Plus I love that Nabble is mostly open source and allows me to
customize many of the features to fit our needs.  

The one major shortfall that I hope doesn't lead to the demise of Nabble is
the ability to run on SSL.  With the ever increasing security concerns on
the internet as well as updated browser warnings for sites that are not
running securely, becoming SSL complaint should be high on the priority
list.  
Blasma will support SSL.  And Blasma will be completely open source, so I hope others contribute and add features.  I will initially focus on the features that I personally use and that doesn't include the email features you mentioned, but features like that should be added over time.  People will be able to move from Nabble to Blasma whenever they want.  One other difference is that with Blasma, each forum will have its own copy of the code and the admin can upgrade whenever he wants, so code changes will cause less problems.
Reply | Threaded
Open this post in threaded view
|

RE: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

Coleen_Astalos

Interesting.  Is there somewhere I can learn more about Blasma?

Coleen

 

From: Franklin <Nabble> [via Nabble Support] [mailto:[hidden email]]
Sent: Tuesday, September 19, 2017 3:35 PM
To: Coleen_Astalos
Subject: RE: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

 

Coleen_Astalos wrote

How about creating a Change Log forum under the support topic and posting
them there?  That would allow the change history to be all in one place (and
allow people to subscribe to just get the change history via email).  

There won't be many changes, so I am just using a thread for this.  You can subscribe to the thread.
 

I'm curious what kinds of changes you have in the works.  We're a pretty
heavy user of Nabble and would be happy to collaborate on changes that might
improve the overall features & benefits of Nabble.  

Right now I am just trying to make Nabble stable enough to that I can then work on other things like Blasma.  This mostly involves removing features that cause trouble.

So far Nabble is unique in its ability to be able to send the forum posts,
in entirety, to the users that have subscribed for email - as well as being
able to post via email (basically interact completely via email, if
desired).  Plus I love that Nabble is mostly open source and allows me to
customize many of the features to fit our needs.  

The one major shortfall that I hope doesn't lead to the demise of Nabble is
the ability to run on SSL.  With the ever increasing security concerns on
the internet as well as updated browser warnings for sites that are not
running securely, becoming SSL complaint should be high on the priority
list.  

Blasma will support SSL.  And Blasma will be completely open source, so I hope others contribute and add features.  I will initially focus on the features that I personally use and that doesn't include the email features you mentioned, but features like that should be added over time.  People will be able to move from Nabble to Blasma whenever they want.  One other difference is that with Blasma, each forum will have its own copy of the code and the admin can upgrade whenever he wants, so code changes will cause less problems.


To unsubscribe from Nabble Error - macro or method for 'report_inappropriate_content_panel' not found, click here.
NAML

Reply | Threaded
Open this post in threaded view
|

RE: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

Franklin <Nabble>
Administrator
Coleen_Astalos wrote
Interesting.  Is there somewhere I can learn more about Blasma?
Not yet.  I want to work on one thing at a time.  I will get to Blasma in about 2 months.  Then I will post about it here.
Reply | Threaded
Open this post in threaded view
|

RE: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

Coleen_Astalos

Great Thanks.

Coleen

Reply | Threaded
Open this post in threaded view
|

RE: Nabble Error - macro or method for 'report_inappropriate_content_panel' not found

harkawy
In reply to this post by Franklin <Nabble>
Franklin,

We are using Nabble on our Weebly site.  We have been informed that we need to go with SSL.
SSL prevents our members from seeing the forum.
If we switch to Blasma, will we be able to transfer our threads from Nabble to Blasma?  How difficult will it be to make the tranfer?

How difficult (or impossible) would it be for Nabble to accept the SSL security as I am sure there are a plethora of Nabble users who need to go to SSL?
In other words, why can't Nabble work with SSL?